Bug 1043632 - Include documentation for switching HornetQ from multicast UDP to TCP
Summary: Include documentation for switching HornetQ from multicast UDP to TCP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER5
: EAP 6.3.0
Assignee: David Michael
QA Contact: Russell Dickenson
David Michael
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 18:53 UTC by dereed
Modified: 2014-08-14 15:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Build Name: 14874, Administration and Configuration Guide-6.2-1 Build Date: 02-12-2013 14:15:34 Topic ID: 5759-299129 [Specified]
Last Closed: 2014-06-28 15:26:58 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description dereed 2013-12-16 18:53:34 UTC 
Title: Use TCP Communication for the Clustering Subsystem

Describe the issue:
Section 16.4 includes documentation on switching JGroups and mod_cluster from multicast UDP to TCP.  But it does not include documentation on doing the same with HornetQ, or even a note that you would also need to.

Suggestions for improvement:
Add documentation for switching HornetQ to TCP to this section.

Additional information:
For starting content, see "Switch from UDP to TCP for HornetQ clustering in JBoss EAP 6"
https://access.redhat.com/site/solutions/293823
Comment 3 Miroslav Novak 2014-05-29 09:25:07 UTC 
Hi David, 

thanks a lot for this procedure. It's looking really good. I've found just one minor thing.

I've followed the guide and when I've started servers then I got exception:
11:12:06,730 ERROR [org.hornetq.core.server] (Old I/O server worker (parentId: -50704508, [id: 0xfcfa4f84, /192.168.40.2:5445])) HQ224018: Failed to create session: HornetQException[errorType=CLUSTER_SECURITY_EXCEPTION message=HQ119099: Unable to authenticate cluster user: HORNETQ.CLUSTER.ADMIN.USER]

This was caused by not setting attribute cluster-password:
<cluster-password>${jboss.messaging.cluster.password:CHANGE ME!!}</cluster-password>

Can you add one more step or notice that cluster-password must be set when security is enabled (it's enabled by default). Otherwise I have no comments.

Thanks,
Mirek
Comment 6 Miroslav Novak 2014-06-03 08:48:11 UTC 
Thanks David! Setting as verified!
Note You need to log in before you can comment on or make changes to this bug.