[
http://jira.jboss.com/jira/browse/JBMESSAGING-960?page=all ]
Sergey Koshcheyev resolved JBMESSAGING-960.
-------------------------------------------
Resolution: Done
Removed bind_addr field. Normally, it will be overridden by JBoss AS setting a system
property. If running messaging standalone (e.g. in tests), we can specify the bind address
explicitly through the jgroups.bind_addr property, or just let JGroups figure it out, in
which case it will use the first non-loopback address it will find.
ClusteredPostOffices are bound to 127.0.0.1 on JGroups config
-------------------------------------------------------------
Key: JBMESSAGING-960
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-960
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.SP1
Reporter: Clebert Suconic
Assigned To: Sergey Koshcheyev
Fix For: 1.2.0.SP2
We should verify what to do with bind-addr:
mcast_addr="228.8.8.8" use_outgoing_packet_handler="true"
loopback="true" ucast_send_buf_size="32000" ip_ttl="32"
bind_addr="127.0.0.1"/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira