powered by Jive Software

NULL pointers in 2.1.3

We upgraded to 2.1.3 about a week ago and since then, we’'ve been getting numerous null pointers in the error log. This eventually causes the server to hang and stop responding to client requests, indefinately. The only way to kill the server is to forcibly kill the java process by sending it a SIG_TERM. The stack traces are below.

2005.05.18 15:24:19 org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:139) Internal server error

java.lang.NullPointerException

at org.jivesoftware.messenger.SessionManager.sessionAvailable(SessionManager.java: 395)

at org.jivesoftware.messenger.ClientSession.setPresence(ClientSession.java:335)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:93)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:150)

at org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:86)

at org.jivesoftware.messenger.PresenceRouter.route(PresenceRouter.java:59)

at org.jivesoftware.messenger.PacketRouter.route(PacketRouter.java:73)

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:240)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)


2005.05.19 13:52:12 org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:139) Internal server error

java.lang.NullPointerException

at org.jivesoftware.messenger.SessionManager.sessionAvailable(SessionManager.java: 397)

at org.jivesoftware.messenger.ClientSession.setPresence(ClientSession.java:335)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:93)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.process(PresenceUpdate Handler.java:150)

at org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:86)

at org.jivesoftware.messenger.PresenceRouter.route(PresenceRouter.java:59)

at org.jivesoftware.messenger.PacketRouter.route(PacketRouter.java:73)

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:240)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)

Hey Micah,

Thanks for the bug report. Could you check in the warn.log file if at the same time there was another problem. My guess is that the socket was closed while authenticating/sending the available presence. Today I added more logging information so it will help if you can try again using tomorrow’'s nightly build. Meanwhile, if you can provide me the steps to follow to reproduce the problem would be great.

Regards,

– Gato