This is slightly off topic, since it seems to be a problem with tomcat.
I have jive messenger set up with jabber http binding (JHB servlet) with tomcat 5.5 and apache, client is jwchat.
It seems that tomcat times out on the sessions and consequently jive disconnects the user (not supposed to happen). i have set the timeout value in the servlets web-inf xml file to something large, but still this happens.
Here’‘s an excerpt from JM’'s debug.log:
2005.11.22 12:00:11 Logging off sabine@jabber.op3racional.info/Sabine@jabber.op3racional.info on org.jivesoftware.messenger.net.SocketConnection@25b72a socket: Socket[addr=/127.0.0.1,port=2783,localport=5222] session: org.jivesoftware.messenger.ClientSession@1950e0a status: 3 address: sabine@jabber.op3racional.info/Sabine@jabber.op3racional.info id: 897ead5d presence:
And what’'s in Tomcats log (no timestamp though):
Session timed out: FQTuFroSTgFhvhRxWMNGocnf
terminating session FQTuFroSTgFhvhRxWMNGocnf
On the client side, we get a 503 service unavailable message.
Is there any way around this issue? Again, any help is greatly appreciated