[ https://issues.apache.org/jira/browse/ZOOKEEPER-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-696: ----------------------------------- Assignee: Patrick Hunt Looks like the issue is that in the tests we are both shutting down the clients and also shutting down the server. As a result in some cases the socket is nulled by one/other of the close calls while the other close call then sees a null for the sock and NPEs. I'll work on a patch. > NPE in the hudson logs, seems nioservercnxn closed twice > -------------------------------------------------------- > > Key: ZOOKEEPER-696 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-696 > Project: Zookeeper > Issue Type: Bug > Components: server > Reporter: Patrick Hunt > Assignee: Patrick Hunt > Priority: Blocker > Fix For: 3.3.0 > > > seeing the following on the console for > http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/729/ > looks like the cnxn is closed twice? (the second time 'sock' is null). > perhaps it's due to client closing and sending session term, then closing > socket, server sees the read return -1, so closes cnxn, then sees the session > close request (which was queued)? > [junit] 2010-03-10 03:15:53,205 - INFO [main:nioserverc...@1232] - > Closed socket connection for client /127.0.0.1:41285 which had sessionid > 0x127461233fc0000 > [junit] 2010-03-10 03:15:53,206 - WARN > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:nioservercnxn$fact...@269] - > Ignoring unexpected runtime exception > [junit] java.lang.NullPointerException > [junit] at > org.apache.zookeeper.server.NIOServerCnxn.close(NIOServerCnxn.java:1232) > [junit] at > org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:594) > [junit] at > org.apache.zookeeper.server.NIOServerCnxn$Factory.run(NIOServerCnxn.java:259) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.