Odd error after partition ran out of space

I’‘m running Jive Messenger 2.2.2 under linux. It’'s using mysql and authenticating against an Active Directory server. It has been working perfectly for months.

Today,. some people were having trouble connecting. Upon investigation, I found out that the partition that jive exists on was at 100%. I fixed this, and restarted Messenger, but one of the users still can’'t connect properly.

If I log into the Admin Console, I can see that the user is authenticated, but neither his jabber client, nor anyone else’‘s roster shows that he’'s online. He has tried connecting from several different jabber clients, on multiple workstations.

Strangely, he’‘s the only user with this problem. Everyone else is working normally. I can only assume that something was corrupted when the partition ran out of space, but I’'m at a loss as to how to fix it. Any ideas?

Thanks in advance.

Here is the output to the error.log when he connects:

2006.01.12 16:46:55 org.jivesoftware.messenger.handler.IQRosterHandler.handleIQ(IQRosterHandler.java :118) Internal server error


at java.util.TreeMap.compare(TreeMap.java:1093)

at java.util.TreeMap.getEntry(TreeMap.java:347)

at java.util.TreeMap.containsKey(TreeMap.java:204)

at java.util.TreeSet.contains(TreeSet.java:196)

at org.jivesoftware.messenger.group.Group.isUser(Group.java:191)

at org.jivesoftware.messenger.roster.Roster.(Roster.java:100)

at org.jivesoftware.messenger.roster.RosterManager.getRoster(RosterManager.java:69 )

at org.jivesoftware.messenger.user.User.getRoster(User.java:243)

at org.jivesoftware.messenger.handler.IQRosterHandler.manageRoster(IQRosterHandler .java:173)

at org.jivesoftware.messenger.handler.IQRosterHandler.handleIQ(IQRosterHandler.jav a:103)

at org.jivesoftware.messenger.handler.IQHandler.process(IQHandler.java:48)

at org.jivesoftware.messenger.IQRouter.handle(IQRouter.java:213)

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

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

at org.jivesoftware.messenger.net.SocketReader.processIQ(SocketReader.java:258)

at org.jivesoftware.messenger.net.ClientSocketReader.processIQ(ClientSocketReader. java:43)

at org.jivesoftware.messenger.net.SocketReader.readStream(SocketReader.java:230)

at org.jivesoftware.messenger.net.SocketReader.run(SocketReader.java:111)

at java.lang.Thread.run(Thread.java:595)

Hey rev138,

I’‘m almost sure that you are running into an already fixed issue. Is there any reason why you haven’‘t updated to the latest Wildfire version? Since you are already using JM 2.2.* you won’'t have to update your database (there is just a small change that can be ignored).


– Gato

The reason I wasn’‘t running the latest version was that (until yesterday) it was working perfectly. I usually like to follow the "if it ain’'t broke…" philosphy with production software.

However, it was broke, and switching to 2.4.1 did the trick.


Message was edited by: