[jboss-jira] [JBoss JIRA] Commented: (JGRP-280) Problem with Multiplexer and state transfer
Bela Ban (JIRA)
jira-events at jboss.com
Fri Aug 25 11:46:51 EDT 2006
[ http://jira.jboss.com/jira/browse/JGRP-280?page=comments#action_12341878 ]
Bela Ban commented on JGRP-280:
-------------------------------
Fixed - needs more debugging to verify it works
> Problem with Multiplexer and state transfer
> -------------------------------------------
>
> Key: JGRP-280
> URL: http://jira.jboss.com/jira/browse/JGRP-280
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.3, 2.3 SP1
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Fix For: 2.4
>
>
> Was looking at server logs from a testsuite run when I noticed something
> odd.
> We've got a 2 node cluster, node0 and node1, running the "all" config.
> Sequence of events:
> 1) node0 starts; as part of normal start of an "all" config 5 different
> services deploy sharing a channel (4 JBC instances + ClusterPartition)
> 2) Then node1 starts, and deploys the same 5 services. All is fine,
> incl state transfers from node0.
> 3) Test driver copies to node0/deploy a sar with 3 more services that
> use the same channel as the previous 5. This goes fine on node0, but on
> node1 I find a bunch of ERROR and WARN messages in the log (see below).
> 4) Test driver copies sar to node1/deploy. The 3 services deploy on
> node1 without problem; no further error messages.
> 5) The test itself passes fine; I just happened to see the following in
> the logs.
> Following are the messages. Looks like 1) node1 gets a state transfer
> request for the BadPartition-TreeCache service, which AFAICT it
> shouldn't. 2) The Multiplexer throws an exception on the request instead
> of logging a WARN, and 3) when the Multiplexer gets a view for a service
> it doesn't have, it logs a WARN, which should probably be an INFO, as
> its not a sign of something wrong in this case.
> 2006-08-20 19:55:00,593 ERROR [STDERR]
> java.lang.IllegalArgumentException: didn't find service with
> ID=BadPartition-TreeCache to fetch state from
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.mux.Multiplexer.handleStateRequest(Multiplexer.java:490)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.mux.Multiplexer.up(Multiplexer.java:260)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.JChannel.up(JChannel.java:1082)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.STATE_TRANSFER.requestApplicationStates(STA
> TE_TRANSFER.java:308)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:137)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.FC.up(FC.java:344)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.GMS.up(GMS.java:753)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:773)
> 2006-08-20 19:55:00,593 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:154)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.protocols.UNICAST.up(UNICAST.java:224)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.passUp(Protocol.java:538)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:428)
> 2006-08-20 19:55:00,609 ERROR [STDERR] at
> org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list