[jboss-jira] [JBoss JIRA] Updated: (JBAS-6307) Cross-cluster cross-talk on JBM-DATA channel
[
https://jira.jboss.org/jira/browse/JBAS-6307?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-6307:
-----------------------------------
Workaround Description:
Replace the complex syntax like:
mcast_addr="${jboss.messaging.datachanneludpaddress,jboss.partition.udpGroup:228.6.6.6}"
with:
mcast_addr="${jboss.partition.udpGroup:228.6.6.6}"
Prefer keeping the jboss.partition.udpGroup property as that can easily be set from the
command line via the -u or --udp startup option.
Workaround: [Workaround Exists]
Cross-cluster cross-talk on JBM-DATA channel
--------------------------------------------
Key: JBAS-6307
URL: https://jira.jboss.org/jira/browse/JBAS-6307
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, JMS (JBoss Messaging)
Affects Versions: JBossAS-5.0.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.0.1.CR1
The configuration syntax in the jbm-data protocol stack config's MPING.mcast_addr
attribute is not understood by the JGroups parser; it's syntax only supported by the
String property replacement code in jboss-common-core.jar.
<MPING timeout="5000"
mcast_addr="${jboss.messaging.datachanneludpaddress,jboss.partition.udpGroup:228.6.6.6}"
will be evaluated by JGroups as "use value for system property
'jboss.messaging.datachanneludpaddress,jboss.partition.udpGroup', if not found use
228.6.6.6". Which results in 228.6.6.6.
Fix is to replace with
<MPING timeout="5000"
mcast_addr="${jboss.partition.udpGroup:228.6.6.6}"
in which case setting -u at AS startup will set jboss.partition.udpGroup, which JGroups
will find and use.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira