Well, I have found a wrinkle...

If I run $JBOSS_HOME/probe.sh, I don't get a listing of the cluster members. 
The application doesn't show any errors, it just behaves/exits normally, just 
as it would if there were no cluster members.

Previously probe.sh gave me a listing of all the members in the cluster.

If I check a server log file, I see:


  | 2007-04-10 11:07:02,262 WARN  [org.jgroups.protocols.UDP] packet from
  | 147.209.225.205:37242 has different version (25705) from ours (241).
  | This may cause problems
  | 2007-04-10 11:07:02,263 ERROR [org.jgroups.protocols.UDP] failed 
unmarshalling message java.io.EOFException
  |         at java.io.DataInputStream.readInt(DataInputStream.java:358)
  |         at org.jgroups.protocols.TP.bufferToList(TP.java:1020)
  |         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:827)
  |         at org.jgroups.protocols.TP.access$400(TP.java:45)
  |         at
  | org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
  |         at java.lang.Thread.run(Thread.java:595)
  | 2007-04-10 11:10:58,178 WARN  [org.jgroups.protocols.UDP] packet from
  | 147.209.225.205:37262 has different version (25705) from ours (241).
  | This may cause problems
  | 

I am going to try setting the compatibility flag 
-Djgroups.marshalling.compatible=true on the command line in probe.sh.

My guess is that this is what happens within JBoss 4.0.5GA which "built the fix 
into GA."?

I did have to hack probe.sh a little: to ensure that it picked up the version 
of jgroups.jar from one of the cluster member's server/lib directories, rather 
than using the one in default/all (forget which it was now...typing at home).

Will report back.

Cheers,

Alph

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036152#4036152

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036152
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to