That's clearly a bug in JGroups. I think I fixed it in 2.4.x. Which version of JGroups
are you running ?
java -cp jgroups.jar org.jgroups.Version
will tell you.
If you use 2.4.1.SP4, this will disappear (probably 2.3 already fixes this issue too).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069490#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...