[jboss-jira] [JBoss JIRA] Commented: (JGRP-636) NullPointerException in Multiplexer
[ http://jira.jboss.com/jira/browse/JGRP-636?page=comments#action_12389286 ]
Vladimir Blagojevic commented on JGRP-636:
------------------------------------------
Robert,
How did this happen? I see that you are using STATE_TRANSFER, VIEW_SYNC, BARRIER protocols
and that the thread that this message arrived on was a socket thread!! Look in the
stacktrace how thread pool rejected running message on its own thread meaning all threads
in the pool were busy!
I am more interested in how you managed to create this situation than this particular
NullPointerException.
Regards.
NullPointerException in Multiplexer
-----------------------------------
Key: JGRP-636
URL: http://jira.jboss.com/jira/browse/JGRP-636
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6
Reporter: Robert Newson
Assigned To: Vladimir Blagojevic
Fix For: 2.7, 2.6.1
java.lang.NullPointerException
at org.jgroups.mux.Multiplexer.handleStateRequest(Multiplexer.java:639)
at org.jgroups.mux.Multiplexer.up(Multiplexer.java:352)
at org.jgroups.JChannel.up(JChannel.java:1148)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:362)
at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:427)
at
org.jgroups.protocols.pbcast.STATE_TRANSFER.requestApplicationStates(STATE_TRANSFER.java:233)
at
org.jgroups.protocols.pbcast.STATE_TRANSFER.handleStateReq(STATE_TRANSFER.java:367)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:117)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:766)
at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:161)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:579)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:250)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:714)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:122)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
at org.jgroups.protocols.FD.up(FD.java:322)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:300)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
at org.jgroups.protocols.Discovery.up(Discovery.java:250)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1510)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1459)
at
java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1737)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at org.jgroups.protocols.TP.dispatchToThreadPool(TP.java:1060)
at org.jgroups.protocols.TP.receive(TP.java:1031)
at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:899)
at java.lang.Thread.run(Thread.java:619)
--
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