[jboss-jira] [JBoss JIRA] Assigned: (JGRP-1113) FLUSH.rejectFlush() throws nullpointer locking up the cluster
Vladimir Blagojevic (JIRA)
jira-events at lists.jboss.org
Tue Dec 15 04:03:31 EST 2009
[ https://jira.jboss.org/jira/browse/JGRP-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Blagojevic reassigned JGRP-1113:
-----------------------------------------
Assignee: Vladimir Blagojevic (was: Bela Ban)
> FLUSH.rejectFlush() throws nullpointer locking up the cluster
> -------------------------------------------------------------
>
> Key: JGRP-1113
> URL: https://jira.jboss.org/jira/browse/JGRP-1113
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.6.13
> Environment: Sun T2000, Solaris 10 u4, Java 1.5 u17
> Reporter: Kaarel Kann
> Assignee: Vladimir Blagojevic
>
> Probably linked to JGRP-1024
> Log of nullpointer happening:
> Received Event[type=SUSPEND, arg=null] at 192.168.188.22:32952. Running FLUSH... [Thread-11]
> Flush coordinator 192.168.188.22:32952 is starting FLUSH with participants [192.168.188.22:32952, 192.168.188.32:32803] [Thread-11]
> At 192.168.188.22:32952 timed out waiting for flush responses after 2000 msec. Rejecting flush to participants null [Thread-11]
> java.lang.NullPointerException [Thread-11]
> at org.jgroups.protocols.pbcast.FLUSH.rejectFlush(FLUSH.java:546) [Thread-11]
> at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:238) [Thread-11]
> at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:222) [Thread-11]
> at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:285) [Thread-11]
> at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:461) [Thread-11]
> at org.jgroups.JChannel.downcall(JChannel.java:1540) [Thread-11]
> at org.jgroups.JChannel.startFlush(JChannel.java:1810) [Thread-11]
> at org.jgroups.JChannel.startFlush(JChannel.java:1866) [Thread-11]
> Log of lockup:
> FLUSH block at 192.168.188.22:32952 for ever [Thread-11]
> Maybe relavant log of bootup error:
> E 1209-0812:32,496 sender 192.168.188.32:32803 not found in xmit_table [Incoming-2,192.168.188.22:32952]
> E 1209-0812:32,504 range is null [Incoming-2,192.168.188.22:32952]
> D 1209-0812:32,507 existing digest: 192.168.188.22:32952: [33 : 38 (38)]
> new digest: 192.168.188.32:32803: [39 : 43 (43)], 192.168.188.22:32952: [33 : 37 (37)]
> resulting digest: 192.168.188.32:32803: [39 : 43 (43)], 192.168.188.22:32952: [33 : 38 (38)] [Incoming-2,192.168.188.22:32952]
> D 1209-0812:32,508 [local_addr=192.168.188.22:32952] view is MergeView::[192.168.188.22:32952|1] [192.168.188.22:32952,
> 192.168.188.32:32803], subgroups=[[192.168.188.22:32952|0] [192.168.188.22:32952], [192.168.188.32:32803|0] [192.168.188
> .32:32803]] [Incoming-2,192.168.188.22:32952]
> D 1209-0812:32,523 Installing view at 192.168.188.22:32952 view is MergeView::[192.168.188.22:32952|1] [192.168.188.22:
> 32952, 192.168.188.32:32803], subgroups=[[192.168.188.22:32952|0] [192.168.188.22:32952], [192.168.188.32:32803|0] [192.
> 168.188.32:32803]] [Incoming-2,192.168.188.22:32952]
> D 1209-0812:32,528 resuming message garbage collection [Incoming-1,192.168.188.22:32952]
> D 1209-0812:32,538 VIEW_CHANGE received: [192.168.188.22:32952, 192.168.188.32:32803] [Timer-2,192.168.188.22:32952]
> D 1209-0812:32,542 first member; cache is empty [FD_SOCK pinger,192.168.188.22:32952]
> D 1209-0812:32,542 determinePingDest()=192.168.188.32:32803 [FD_SOCK pinger,192.168.188.22:32952]
> D 1209-0812:32,554 192.168.188.22:32952 sending RESUME event [MergeTask,192.168.188.22:32952]
> D 1209-0812:32,555 Received RESUME at 192.168.188.22:32952, sent STOP_FLUSH to all [MergeTask,192.168.188.22:32952]
> D 1209-0812:32,555 Merge leader 192.168.188.22:32952 completed merge task [MergeTask,192.168.188.22:32952]
> D 1209-0812:32,557 ping_dest=192.168.188.32:32803, ping_sock=Socket[addr=/192.168.188.32,port=34281,localport=35828], cache={192.168.188.32:32803=192.168.188.32:34281, 192.168.188.22:32952=192.168.188.22:34307} [FD_SOCK pinger,192.168.188.22:32952]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list