[jboss-jira] [JBoss JIRA] (JGRP-1512) RELAY2: Invalid message type when delivered from a node in one geo location to a node in another

Jiri Pechanec (JIRA) jira-events at lists.jboss.org
Wed Sep 12 04:44:32 EDT 2012


Jiri Pechanec created JGRP-1512:
-----------------------------------

             Summary: RELAY2: Invalid message type when delivered from a node in one geo location to a node in another
                 Key: JGRP-1512
                 URL: https://issues.jboss.org/browse/JGRP-1512
             Project: JGroups
          Issue Type: Bug
    Affects Versions: 3.2
         Environment: jgroups-3.2.0.Alpha1.jar 
Fedora 14, Solaris 10

java version "1.6.0_20" 
OpenJDK Runtime Environment (IcedTea6 1.9.10) (fedora-55.1.9.10.fc14-x86_64) 
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) 

java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) Server VM (build 14.3-b01, mixed mode)
            Reporter: Jiri Pechanec
            Assignee: Bela Ban


I tried to simulate geo cluster using RELAY2.
Configuration files are attached and were developed from vanilla udp.xml and tcp.xml.
The cluster setup
two machines
10.34.3.135
10.34.40.20
Each machines run two instances of Chat demo. One with plain UDP stack bound to localhost (node1 and node2), second with mixed UDP stack bound to localhost and RELAY2 bridge (bridge1 and bridge2) to the other machine.

When the cluster is formed I tried to send a message 'testmessage' from node2 (Solaris machine) to node1 (Fedora machine). The message was properly delivered to bridge2 (Solaris) and bridge1 (Fedora) but on the node1 (Fedora) an exception is thrown
{noformat}
SEVERE: couldn't deliver message [dst: <null>, src: jpechane-28748 (3 headers), size=21 bytes]
java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: type 4 is invalid
        at org.jgroups.Message.getObject(Message.java:378)
        at org.jgroups.demos.Chat.receive(Chat.java:19)
        at org.jgroups.JChannel.invokeCallback(JChannel.java:757)
        at org.jgroups.JChannel.up(JChannel.java:718)
        at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1020)
        at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:178)
        at org.jgroups.protocols.RSVP.up(RSVP.java:188)
        at org.jgroups.protocols.FRAG2.up(FRAG2.java:181)
        at org.jgroups.protocols.FlowControl.up(FlowControl.java:400)
        at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
        at org.jgroups.protocols.pbcast.GMS.up(GMS.java:899)
        at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244)
        at org.jgroups.protocols.UNICAST.up(UNICAST.java:414)
        at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:742)
        at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:536)
        at org.jgroups.protocols.BARRIER.up(BARRIER.java:126)
        at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143)
        at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:177)
        at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288)
        at org.jgroups.protocols.MERGE2.up(MERGE2.java:205)
        at org.jgroups.protocols.Discovery.up(Discovery.java:359)
        at org.jgroups.protocols.TP.passMessageUp(TP.java:1210)
        at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1774)
        at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1742)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.IllegalArgumentException: type 4 is invalid
        at org.jgroups.util.Util.objectFromByteBuffer(Util.java:463)
        at org.jgroups.Message.getObject(Message.java:375)
        ... 26 more
{noformat}

Log files for all instances are attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list