powered by Jive Software

Wildfire 3.0.0 problems on user connection

Have upgraded on Wednesday 2.6.2 > 3.0.0

I had one user already in db. Today i have configured Exodus, it has connected but all contacts were offline, so i tried to close Exodus and connect again, but it said that pass is worng or username is already in use. In Admin Console connection was Closed. I tried to close it anyway. No help. After a while it connected again but all list was offline. After a minute some of contacts got Online, but not everyone which are online. Dont know if this is some problem with that PC. Here some errors.

Today 2 more people have complained that they got error about wrong pass or that threir user is in use already. Strange. The load should be the same as always. So i think this is probably something with Wildfire and not with hardware limitations.

2006.07.10 09:26:01 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:7 29)

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.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)

Cant imagine how to reproduce. Maybe to upgrade 2.6.2 to 3.0.0 Because errors appear with random old users, like this:

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

2006.07.12 17:15:35 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:7 27)

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.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(Unknown Source)

Users dont complain. But all pur Exoduses are starting with the same unchanged config everytime. This config was created when first connecting new user and saved and startup script is copying this “good” config at every startup. This was done long long time ago when there were problems to reconnect to Jive Messenger after connection loss. Exodus was deleting password in config somehow. Wasnt able to find out the reasons so such workaround was implemented. Dont remember, maybe such errors were here all the time. But it looks the same like that in first message, when i wasnt able to get roster presences.

Havent noticed this for a long. Closing

Wonder. Is there some mechanism marking thread as archived qiocker than others if there is no replies of other users?:slight_smile: Cause some of my older threads are not archived, but there are replies of others.