[jboss-jira] [JBoss JIRA] Commented: (JBAS-6307) Cross-cluster cross-talk on JBM-DATA channel

[Kevin Lohmann (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575201#comment-12575201 ] 

Kevin Lohmann commented on JBAS-6307:
-------------------------------------

I'm using JBoss AS 5.1.0 EAP.

If I'm not wrong, this version doesn't contain this fix.

> Cross-cluster cross-talk on JBM-DATA channel
> --------------------------------------------
>
>                 Key: JBAS-6307
>                 URL: https://issues.jboss.org/browse/JBAS-6307
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, JMS (HornetQ)
>    Affects Versions: JBossAS-5.0.0.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.0.1.GA
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira