Hello,
I have detected this error during loadtesting of wildfire (2.6.2 and 3.0.1) with tsung 1.2
- in warn.log :
2006.08.22 08:42:23 No SessionMap found for session
org.jivesoftware.wildfire.ClientSession@76a29a7 status: -1 address: user4009@IP/tsung id: 8e670f8d presence:
- in tomcat log (wildfire is running in tomcat):
Internal server error. Triggered by packet:
java.lang.NullPointerException
at org.jivesoftware.wildfire.SessionManager.sessionAvailable(SessionManager.java:7 27)
at org.jivesoftware.wildfire.ClientSession.setPresence(ClientSession.java:661)
at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:98)
at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:153)
at org.jivesoftware.wildfire.PresenceRouter.handle(PresenceRouter.java:92)
at org.jivesoftware.wildfire.PresenceRouter.route(PresenceRouter.java:61)
at org.jivesoftware.wildfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:75)
at org.jivesoftware.wildfire.net.SocketReader.processPresence(SocketReader.java:29 6)
at org.jivesoftware.wildfire.net.ClientSocketReader.processPresence(ClientSocketRe ader.java:57)
at org.jivesoftware.wildfire.net.SocketReader.process(SocketReader.java:191)
at org.jivesoftware.wildfire.net.BlockingReadingMode.readStream(BlockingReadingMod e.java:156)
at org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 62)
at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:123)
at java.lang.Thread.run(Thread.java:595)
in org.jivesoftware.wildfire.SessionManager.sessionAvailable:
…
SessionMap sessionMap = sessions.get(session.getUsername());
if (sessionMap == null) {
Log.warn(“No SessionMap found for session” + “\n” + session);
}
// Update the order of the sessions based on the new presence of this session
sessionMap.sessionAvailable(session);
…
so if sessionMap is null , it will always throw a NPE
I think , there is a so big load in wildfire , that the server tries to send a presence packet from a user which has just closed its connection after having sent the presence packet …
Is it normal ? or is it a bug ?
Does anyone meet this problem before ?
Message was edited by: usermich