Server randomly drops connections

I’m running Openfire 3.3.2 (on windows) and every morning it drops all of the connections and boots everyone from the conference rooms.

In the warn log there are 12 of these:

2007.08.10 07:54:13 Closing session due to incorrect hostname in stream header. Host: Connection: socket: Socket[http://addr=/,port=3706,localport=5269|http://addr=/,por t=3706,localport=5269] session: null

And in the error log there are 12 of these:

2007.08.10 07:54:13 [org.jivesoftware.openfire.session.OutgoingServerSession.createOutgoingSession(

] Error trying to connect to remote server: lookup:

at Source)

at Source)

at Source)

at org.jivesoftware.openfire.session.OutgoingServerSession.createOutgoingSession(O

at org.jivesoftware.openfire.session.OutgoingServerSession.authenticateDomain(Outg

at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(

at org.jivesoftware.openfire.server.OutgoingSessionPromise$

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$ Source)

at Source)

And in the spark log (note the timestamp is different?)

Aug 9, 2007 7:43:17 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Connection closed on error. Read timed out

at Method)

at Source)

at Source)

at Source)

at Source)

at Source)

at Source)

at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)

at sun.nio.cs.StreamDecoder.implRead(Unknown Source)

at Source)

at Source)

at Source)

at Source)

at Source)

at org.xmlpull.mxp1.MXParser.fillBuf(

at org.xmlpull.mxp1.MXParser.more(

at org.xmlpull.mxp1.MXParser.nextImpl(


at org.jivesoftware.smack.PacketReader.parsePackets(

at org.jivesoftware.smack.PacketReader.access$000(

at org.jivesoftware.smack.PacketReader$

Now if I understand correctly, doesn’t actually have to be in DNS does it, thats what the SRV records are for? Why is it doing a lookup?

I’m hoping there are some clues to resolving this in the above logs as its frustrating to have to ask everyone to re-join the conference every morning.

Hey aelix,

I think that you are seeing 2 different issues: 1) dropped connections and 2) unknown s2s traffic.

Dropped connections

By default, Openfire closes connections that have been idle for 6 minutes. Clients that send heartbeats to the server do not get their connections closed. If that is not your problem then remember that Openfire will also kick idle room occupants after an inactivity of 30 minutes. You can change this setting from the admin console ( Group chat --> Other Settings ). Another option is that there is a firewall between the clients and the server that is closing long lived connections or idle connections. Any of the previously mentioned issues will remove occupants from the room.

Unknown s2s traffic

If your server domain is not then any packet sent to will end up in a server-2-server traffic. The error you are seeing is that the server attempted to connect to and failed. Openfire will then try to connect to assuming that that server is hosting the conference service.


– Gato