Exodus Client

Hi Folks,

What kind of configuration may I do in order to avoid the “Events pop-up window” to appear when Exodus Client logs on the server?

Exodus Client: 0.9.1.0

Regards,

Eduardo

Are you talking about notification pop-up when users go online?

If so, Tools > Options > Notification and uncheck “Contact came online”.

If that’‘s not the case and you are talking about Events window with offline messages queued up in it. Try Tools > Options > Messages and uncheck “Queue all offline messages (even chats)”. But this not helps when there are a lot of messages. And i’'m having some anomality when very old messages appears in such Events pop-up time to time.

that’‘s it what I’'m talking about… I´m having the same problem. Sometimes Exodus does not respond when these events pop-up messages appear.

Regards

Eduardo

that’'s my thread:

http://www.jivesoftware.org/forums/thread.jspa?threadID=15249&tstart=0

but nothing is clear, though in my case Exodus is working normally after such pop-up

Hey guys,

Is the server sending those messages to Exodus or is this something that Exodus does by its own? Could you open the debug window in Exodus (F12) and past the XML packets that the server is sending and it shouldn’'t be sending? BTW, any error in the log files?

Regards,

– Gato

well, this behavior is occasional (very rare), so you’'ll have to wait till i have some usefull debug or logs. I will post it in my thread if this will repeat.

Gato,

It happens occasionally in my Exodus too as Wroot said before. But, When I always connect to JM 2.2.1, the error.log always shows these messages below:

2005.09.06 08:44:51 [org.jivesoftware.messenger.OfflineMessageStore.getMessages(OfflineMessageStore .java:185)

] Internal server error

org.dom4j.DocumentException: Error on line 3 of document : An invalid XML character (Unicode: 0x1c) was found in the element content of the document. Nested exception: An invalid XML character (Unicode: 0x1c) was found in the element content of the document.

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

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

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

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

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

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

at org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:87)

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

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

at org.jivesoftware.messenger.net.SocketReader.processPresence(SocketReader.java:3 01)

at org.jivesoftware.messenger.net.ClientSocketReader.processPresence(ClientSocketR eader.java:49)

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

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

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

Nested exception:

org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1c) was found in the element content of the document.

at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseExcep tion(Unknown Source)

at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source)

at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)

at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)

at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragment ContentDispatcher.dispatch(Unknown Source)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocu ment(Unknown Source)

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

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

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

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

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

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

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

at org.jivesoftware.messenger.PresenceRouter.handle(PresenceRouter.java:87)

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

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

at org.jivesoftware.messenger.net.SocketReader.processPresence(SocketReader.java:3 01)

at org.jivesoftware.messenger.net.ClientSocketReader.processPresence(ClientSocketR eader.java:49)

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

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

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

Do these messages have something to do with this?

Thanks in advance,

Eduardo