[jboss-jira] [JBoss JIRA] (JGRP-1443) Null pointer exception testing proposed fix for JGRP-1426

[David Hotham (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Hotham reopened JGRP-1443:
--------------------------------



Per remarks in JGRP-1426, I've hit this NPE:

-  with and without the 1426 fix
-  with and without FLUSH being in the stack

So I'm reopening it: I think we should view it as an independent bug.

I'm currently using 3.1.0.Beta1, with a stack that goes:

TCP
TCPPING
MERGE3
FD_SOCK
FD
NACKACK2
UNICAST2
STABLE
SEQUENCER
GMS
UFC
MFC
FRAG2

I don't have a test script that reproduces this without FLUSH being in the stack.  However I am able to hit it live reasonably reliably, by having a cluster of four members and killing two of them (not the coordinator) as close together as I can.

I can try to work on a scripted repro if necessary.  Let me know if you need me to do that.
                
> 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.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