[
http://jira.jboss.com/jira/browse/JGRP-792?page=comments#action_12419093 ]
Wojciech Meler commented on JGRP-792:
-------------------------------------
I''m confused. What is the reason for having such priority order where global
system properties are more important than local component configuration even if such
behavior can be specified in local configuration when needed?
JGroups ignores mcast_addr attribute in XML when
"jgroups.udp.mcast_addr" is set
--------------------------------------------------------------------------------
Key: JGRP-792
URL:
http://jira.jboss.com/jira/browse/JGRP-792
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.2
Environment: linux, JDK 1.6, JBoss 4.2.1.GA
Reporter: Jacek Gerbszt
Assigned To: Bela Ban
JGroups seems to ignore mcast_addr attribute of <UDP/> element in XML configuration
file used as a parameter in JChannel constructor, when the system property
"jgroups.udp.mcast_addr" is set.
This behaviour has been observed on JBoss 4.2.1.GA started with an argument: -u
239.192.0.5. I'm trying to connect to group in the start() method of my MBean:
public void start() throws ChannelException {
channel = new JChannel("my-udp.xml");
channel.connect("MyGroup");
UDP udp = (UDP) channel.getProtocolStack().findProtocol(UDP.class);
log.info(udp.getInfo());
}
Unfortunately log.info() shows that channel is connected to 239.192.0.5 instead of IP
configured in my-udp.xml.
It is a big problem when you want to connect from jboss to two different groups with two
different multicast addresses.
--
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