[jboss-jira] [JBoss JIRA] (JGRP-1443) Null pointer exception testing proposed fix for JGRP-1426
[
https://issues.jboss.org/browse/JGRP-1443?page=com.atlassian.jira.plugin....
]
David Hotham commented on JGRP-1443:
------------------------------------
Still hitting problems, I'm afraid...
Just to remind you of my testcase:
- I have a group with three ever-present members A, B, C
- members D and E take it in turns to try and join the group, wait for the view to
settle, and be killed
- everyone broadcasts a message every few seconds
The NPE reported here was hit by one of the ever-presents.
When I came in this morning, I found that member E was using all of the CPU on one of my
cores (and had failed to join the group). Presumably some thread is tight-looping.
Sadly, jstack / jconsole etc (I'm on Windows) were unable to attach to the process so
I haven't been able to get any more useful insight into where the problem is.
I suppose we have one of:
- something about the fix you've made on the ever-presents causes the joiner to tight
loop
- a new problem
Can you please advise?
- would you like to track this issue under a new ticket, or do you think it's likely
to be all part of the same thing?
- what trace would be useful?
Thanks!
Null pointer exception testing proposed fix for JGRP-1426
---------------------------------------------------------
Key: JGRP-1443
URL: https://issues.jboss.org/browse/JGRP-1443
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.8
Reporter: David Hotham
Assignee: Bela Ban
Fix For: 3.0.9, 3.1
Attachments: jgroups-3.0.9.Final.jar
Per email exchange: testing a proposed fix for JGRP-1426, I hit the following exception:
SEVERE: failed sending message to 10.239.0.5 (185 bytes):
java.lang.NullPointerException, cause: null
java.lang.NullPointerException
at org.jgroups.protocols.pbcast.JoinRsp.writeTo(JoinRsp.java:90)
at org.jgroups.util.Util.writeStreamable(Util.java:934)
at org.jgroups.protocols.pbcast.GMS$GmsHeader.writeTo(GMS.java:1155)
at org.jgroups.Message.writeHeader(Message.java:891)
at org.jgroups.Message.writeTo(Message.java:698)
at org.jgroups.protocols.TP.writeMessage(TP.java:1367)
at org.jgroups.protocols.TP.send(TP.java:1279)
at org.jgroups.protocols.TP.down(TP.java:1138)
at org.jgroups.protocols.Discovery.down(Discovery.java:573)
at org.jgroups.protocols.TCPPING.down(TCPPING.java:108)
at org.jgroups.protocols.MERGE3.down(MERGE3.java:242)
at org.jgroups.protocols.FD.down(FD.java:308)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:80)
at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:493)
at org.jgroups.protocols.UNICAST2.down(UNICAST2.java:502)
at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:328)
at org.jgroups.protocols.pbcast.GMS.sendJoinResponse(GMS.java:543)
at
org.jgroups.protocols.pbcast.CoordGmsImpl.handleMembershipChange(CoordGmsImpl.java:156)
at org.jgroups.protocols.pbcast.GMS$ViewHandler.process(GMS.java:1390)
at org.jgroups.protocols.pbcast.GMS$ViewHandler.run(GMS.java:1344)
at java.lang.Thread.run(Thread.java:662)
You said:
{quote}
ah, ok, this is a change I made recently, to reduce the size of digests.
Can you open a JIRA so we can track this ?
I'll fix it this week.
{quote}
... so here we are.
Thanks!
David
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira