powered by Jive Software

Exceptions in 2.1.4

Here are some exceptions we’'ve been noticing in the server logs. Thankfully, jive is written in Java otherwise it would crash with segfaults everyday. ;o)


org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)

at org.dom4j.io.SAXReader.read(SAXReader.java:465)

at org.dom4j.io.SAXReader.read(SAXReader.java:365)

at org.jivesoftware.messenger.OfflineMessageStore.getMessages(OfflineMessageStore. java:147)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.initSession(PresenceUp dateHandler.java:206)

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

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

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)


org.dom4j.DocumentException: The node “org.dom4j.tree.DefaultElement@1ab2b55 [Element: ]” could not be added to the branch “null” because: Cannot add another element to this Document as it already has a root element of: thread

at org.dom4j.io.SAXReader.read(SAXReader.java:484)

at org.dom4j.io.SAXReader.read(SAXReader.java:365)

at org.jivesoftware.messenger.OfflineMessageStore.getMessages(OfflineMessageStore. java:147)

at org.jivesoftware.messenger.handler.PresenceUpdateHandler.initSession(PresenceUp dateHandler.java:206)

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

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

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)


java.lang.NullPointerException

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

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

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

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

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.06.24 10:25:50 org.jivesoftware.messenger.handler.IQRosterHandler.handleIQ(IQRosterHandler.java :118) Internal server error

java.lang.NullPointerException

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

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:202)

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

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

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

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

2.1.4? The latest stable release is 2.1.5 (even 2.2.0 Beta 1).

Hey guys,

Gato just figured out this issue and it will be fixed for 2.2.1. It turns out that there’‘s a method that we assumed was thread safe that isn’‘t. So, fairly simple fix. In most cases, seeing this error in the logs shouldn’'t be a big deal but at least it will be gone with the new version.

-Matt

The issue for this problem is JM-364. I will try to fix it today.

Regards,

– Gato

Hey Micah,

The issue has been fixed. You can try again using the next nightly build.

Regards,

– Gato