Ignite Realtime

powered by Jive Software

Ignite Realtime Community Forums

Internal Server Error. Triggered by packet

Openfire Openfire Support

wroot March 31, 2006, 5:52am 1

Still 2.5.0 on my production server. Should i better wait for 2.6.0 than upgrade today?

Some errors:

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:151)

at org.jivesoftware.wildfire.PresenceRouter.handle(PresenceRouter.java:92)

at org.jivesoftware.wildfire.PresenceRouter.route(PresenceRouter.java:61)

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

at org.jivesoftware.wildfire.net.SocketReader.processPresence(SocketReader.java:44 3)

at org.jivesoftware.wildfire.net.ClientSocketReader.processPresence(ClientSocketRe ader.java:56)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:240)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

2006.03.30 13:59:55 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:159) Connection closed before session established

Socket[addr=/192.168.12.82,port=1739,localport=5222]

2006.03.30 14:16:28 org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateHa ndler.java:139) Internal server error. Triggered by packet:

java.lang.NullPointerException

at org.jivesoftware.wildfire.SessionManager.sessionAvailable(SessionManager.java:5 74)

at org.jivesoftware.wildfire.ClientSession.setPresence(ClientSession.java:653)

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:96)

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:151)

at org.jivesoftware.wildfire.PresenceRouter.handle(PresenceRouter.java:92)

at org.jivesoftware.wildfire.PresenceRouter.route(PresenceRouter.java:61)

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

at org.jivesoftware.wildfire.net.SocketReader.processPresence(SocketReader.java:44 3)

at org.jivesoftware.wildfire.net.ClientSocketReader.processPresence(ClientSocketRe ader.java:56)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:240)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

2006.03.30 14:16:32 org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateHa ndler.java:139) Internal server error. Triggered by packet:

java.lang.NullPointerException

at org.jivesoftware.wildfire.SessionManager.sessionAvailable(SessionManager.java:5 72)

at org.jivesoftware.wildfire.ClientSession.setPresence(ClientSession.java:653)

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:96)

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:151)

at org.jivesoftware.wildfire.PresenceRouter.handle(PresenceRouter.java:92)

at org.jivesoftware.wildfire.PresenceRouter.route(PresenceRouter.java:61)

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

at org.jivesoftware.wildfire.net.SocketReader.processPresence(SocketReader.java:44 3)

at org.jivesoftware.wildfire.net.ClientSocketReader.processPresence(ClientSocketRe ader.java:56)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:240)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

P.S. as we having more and more users every day there can be some problems while our server is only with 64MB RAM. I’'ve read in forum that OutOfMemory errors can lead to problems with presences, etc., arent they? Sometimes some users are having problems. Presences not updating, or roster all offline. Where should this OutOfMemory error should appear? In Wildfire logs or system?

LG1 March 31, 2006, 9:21pm 2

Hi Oleg,

you are running linux and Wifi, aren’'t you?

The JVM writes those errors usually to STDERR as it can’'t write it somewhere else. If you are using the default wildfire start script you should find them in nohup.out.

The application may catch some OutOfMemory errors, so they would appear also in the error.log.

LG

wroot April 12, 2006, 10:43am 3

Have upgraded to 2.6.0 on Friday and cleared all logs. So far i have these:

warn.log

2006.04.10 17:18:38 No SessionMap found for session

org.jivesoftware.wildfire.ClientSession@10dae16 status: -1 address: user1@jiveserver/Exodus id: 7daa45b1 presence:

error.log

2006.04.10 17:18:42 org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateHa ndler.java:141) Internal server error. Triggered by packet:

java.lang.NullPointerException

at org.jivesoftware.wildfire.SessionManager.sessionAvailable(SessionManager.java:5 71)

at org.jivesoftware.wildfire.ClientSession.setPresence(ClientSession.java:655)

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.PacketRouter.route(PacketRouter.java:73)

at org.jivesoftware.wildfire.net.SocketReader.processPresence(SocketReader.java:44 5)

at org.jivesoftware.wildfire.net.ClientSocketReader.processPresence(ClientSocketRe ader.java:56)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:242)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

Again some internal server error.

wroot April 14, 2006, 12:31pm 4

new one warn.log content

2006.04.14 11:25:34 SaslException

javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.

at com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(Unknown Source)

at com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(Unknown Source)

at org.jivesoftware.wildfire.net.SASLAuthentication.doHandshake(SASLAuthentication .java:204)

at org.jivesoftware.wildfire.net.SocketReader.authenticateClient(SocketReader.java :317)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:278)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

2006.04.14 11:25:50 SaslException

javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.

at com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(Unknown Source)

at com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(Unknown Source)

at org.jivesoftware.wildfire.net.SASLAuthentication.doHandshake(SASLAuthentication .java:204)

at org.jivesoftware.wildfire.net.SocketReader.authenticateClient(SocketReader.java :317)

at org.jivesoftware.wildfire.net.SocketReader.readStream(SocketReader.java:278)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:119)

at java.lang.Thread.run(Unknown Source)

that was with 2.6.0, now 2.6.1

wroot May 10, 2007, 3:50pm 5

As nobody is interested (except of LG, but he’‘s interested in everything:)), and this thread is really old, and i’'m with new machine now (though with new problems). Closing.