Fix periodic remote-stream-error issue

GoogleCodeExporter commented 9 years ago

After ~5 minutes the stream terminates with a 404 response, and the debug
console says:

[2] sending response [848]: <body xmlns="http://jabber.org/protocol/httpbind"/>
[2] inQueue: </stream:stream>
[Fatal Error] :1:30: The element type "doc" must be terminated by the
matching end-tag "</doc>".
[2] terminating session T7MCIblLMpmLJCwZzH5DGs1K
[2] sending response [849]: <body
xmlns="http://jabber.org/protocol/httpbind" condition="remote-stream-error"
type="terminate"/>

The behavior happens both on Jetty and Tomcat. The problem is most likely
with the JHB servlet. If that's the case, a bug in their tracker should be
opened

Original issue reported on code.google.com by h.iver...@gmail.com on 10 Feb 2008 at 5:52

GoogleCodeExporter commented 9 years ago

periodically sending data (a presence packet, for example) fixes the problem:

var intId = setInterval( function() { soashable.con.send( new
Xmpp4Js.Packet.Presence() ); }, 30000 );

 could be a setting in openfire (idle time, etc)

Original comment by h.iver...@gmail.com on 11 Feb 2008 at 3:32

GoogleCodeExporter commented 9 years ago

I found this Openfire property list and there was a client idle setting.

http://www.igniterealtime.org/community/docs/DOC-1061

I added the following property to Openfire and the issue was resolved:

xmpp.client.idle = -1

Original comment by h.iver...@gmail.com on 11 Feb 2008 at 4:04

Changed state: Fixed

Davletvm / soashable

Fix periodic remote-stream-error issue #43