2 Replies Latest reply on Nov 5, 2012 10:26 AM by rhusar

    jboss cluster - failed handling incoming message (JBoss 5.1.0 GA)

    tfrastia
    tfrastia Mar 5, 2010 6:09 AM

      Hello,

       

      I have a cluster with two nodes just call them node1 and node2.

       

      1.Start node1 with command line:

       

      ./bin/run.sh -c all -g DevBaPartitions -u 239.255.200.101 -Djboss.hapartition.mcast_port=20100 -Djboss.webpartition.mcast_port=20300 -Djboss.ejb3entitypartition.mcast_port=20600 -Djboss.ejb3sfsbpartition.mcast_port=20900 -b 10.110.6.66 -Djboss.messaging.ServerPeerID=10 &

       

      ,everything is ok, server is started.

       

      2.Start node2 with command line:


      ./bin/run.sh -c all -g DevBaPartitions -u 239.255.200.101 -Djboss.hapartition.mcast_port=20100 -Djboss.webpartition.mcast_port=20300 -Djboss.ejb3entitypartition.mcast_port=20600 -Djboss.ejb3sfsbpartition.mcast_port=20900 -b 10.110.6.142 -Djboss.messaging.ServerPeerID=20 &

       

      but after start node2, shows warnings for node2 and node1 shows errors...

       

       

      log from node1:
      2010-02-05 22:10:45,903 ERROR [org.jgroups.protocols.UDP] (OOB-4,10.110.6.66:33890) failed handling incoming message
      java.io.IOException: failed reading header
              at org.jgroups.Message.readHeader(Message.java:757)
              at org.jgroups.Message.readFrom(Message.java:643)
              at org.jgroups.protocols.TP.readMessage(TP.java:1502)
              at org.jgroups.protocols.TP.access$700(TP.java:49)
              at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1804)
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
              at java.lang.Thread.run(Thread.java:595)
      Caused by: java.io.EOFException
              at java.io.DataInputStream.readShort(DataInputStream.java:287)
              at org.jgroups.Message.readHeader(Message.java:734)
              ... 7 more
      2010-02-05 22:10:45,908 ERROR [org.jgroups.protocols.UDP] (OOB-4,10.110.6.66:33890) failed handling incoming message
      java.io.IOException: failed reading header
              at org.jgroups.Message.readHeader(Message.java:757)
              at org.jgroups.Message.readFrom(Message.java:643)
              at org.jgroups.protocols.TP.readMessage(TP.java:1502)

       

      log from node2:
      2010-02-05 17:52:21,397 INFO  [org.jboss.mail.MailService] (main) Mail Service bound to java:/Mail
      2010-02-05 17:52:23,716 INFO  [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] (main) SNMP agent going active
      2010-02-05 17:52:32,398 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DevBaPartitions] (main) Initializing partition DevBaPartition
      s
      2010-02-05 17:52:33,018 INFO  [org.jboss.cache.jmx.PlatformMBeanServerRegistration] (main) JBossCache MBeans were successfully registered
      to the platform mbean server.
      2010-02-05 17:52:33,299 INFO  [STDOUT] (JBoss System Threads(1)-3)
      ---------------------------------------------------------
      GMS: address is 10.110.6.142:49214 (cluster=DevBaPartitions)
      ---------------------------------------------------------
      2010-02-05 17:52:33,321 INFO  [STDOUT] (main)
      ---------------------------------------------------------
      GMS: address is 10.110.6.142:49214 (cluster=DevBaPartitions-HAPartitionCache)
      ---------------------------------------------------------
      2010-02-05 17:52:36,433 WARN  [org.jgroups.protocols.pbcast.GMS] (main) join(10.110.6.142:49214) sent to 10.110.6.66:33890 timed out (afte
      r 3000 ms), retrying
      2010-02-05 17:52:36,443 WARN  [org.jgroups.protocols.pbcast.GMS] (JBoss System Threads(1)-3) join(10.110.6.142:49214) sent to 10.110.6.66:
      33890 timed out (after 3000 ms), retrying
      2010-02-05 17:52:39,443 WARN  [org.jgroups.protocols.pbcast.GMS] (main) join(10.110.6.142:49214) sent to 10.110.6.66:33890 timed out (afte
      r 3000 ms), retrying

       

       

      Does anyboby have some idea what with this?

      Thanks.