Hello,
we have two separate clusters running where a client from the first cluster
wants to look up a bean in HA-JNDI from the second one.
After an upgrade from 4.0.0 to 4.0.2, the AutoDiscovery feature doesn't work
anymore.
JBoss 4.0.0 starts up with this message:
2005-06-06 09:51:31,359 INFO
[org.jboss.ha.jndi.DetachedHANamingService$AutomaticDiscovery] Listening on
/192.168.0.1:1102, group=230.0.0.4, HA-JNDI address=192.168.0.1:1100
netstat -a -n gives:
udp 0 0 0.0.0.0:1102 0.0.0.0:*
and everything is fine.
JBoss 4.0.2 comes up with that message:
2005-06-06 09:25:23,868 INFO
[org.jboss.ha.jndi.DetachedHANamingService$AutomaticDiscovery] Listening on
/0.0.0.0:1102, group=230.0.0.4, HA-JNDI address=192.168.0.1:1100
netstat -a -n gives:
udp 0 0 192.168.0.1:1102 0.0.0.0:*
The (new) attribute AutoDiscoveryBindAddress in cluster-service.xml is set to:
<attribute name="AutoDiscoveryBindAddress">${jboss.bind.address}</attribute>
Changing this attribute has no impact.
A network trace shows the client sending a UDP packet
"GET_ADDRESS:TestPartition" to 230.0.0.4:1102, but no server answeres.
Clustering is working fine. OS is RH EL 3.0.
Any hints are really appreciated.
Thanks,
Mathias.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880378#3880378
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880378
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
