Openfire looses connection to client

Openfire Openfire Support
#1

Hello,

we are planing to use openfire for production but still have serious problems.

Our clients get reset and are not connected to openfire any more. It looks like it is happening every hour.

I’m using Linux Redhat RHEL4/U5 with latest openfire rpm.

There are only 4-5 concurrent user logged in yet. Every user has one 1-3 gateway connections via either icq/yahoo/irc. The errors are as follows:

2007.08.23 11:20:56 Connection closed on Error

java.io.EOFException: no more data available - expected end tag </stream:stream> to close start tag stream:stream from line 1, parser stopped on END_TAG seen …… @1:756

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3014)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:419)

at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)

at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:77)

2007.08.23 12:22:55 Connection closed on Error

java.io.EOFException: no more data available - expected end tag </stream:stream> to close start tag stream:stream from line 1, parser stopped on END_TAG seen …… @1:756

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3014)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:419)

at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)

at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:77)

2007.08.23 13:19:59 Connection closed on Error

java.io.EOFException: no more data available - expected end tag </stream:stream> to close start tag stream:stream from line 1, parser stopped on END_TAG seen …… @1:756

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3014)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:419)

at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)

at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:77)

2007.08.23 14:21:28 Connection closed on Error

java.io.EOFException: no more data available - expected end tag </stream:stream> to close start tag stream:stream from line 1, parser stopped on END_TAG seen …… @1:756

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3014)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:419)

at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)

at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:77)

2007.08.23 15:20:33 Connection closed on Error

java.io.EOFException: no more data available - expected end tag </stream:stream> to close start tag stream:stream from line 1, parser stopped on END_TAG seen …… @1:756

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3014)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:419)

at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)

at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:77)

2007.08.22 17:20:30 Connection closed on Error

I didn’t raise memory allocation by java because there are free resources left:

17.78 MB of 63.31 MB (28.1%) used

Any ideas??

Thanks for your help.

#2

Looks like the server needs a xmpp.client.idle=-1. If not some clients are somehow thrown out. Don’t know if this is a bug or not but after setting this nobody is getting thrown out any more.

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

#3

Thanks for posting that, this was happening to my users as well. And the fix has resolved the issue as well.

#4

kaffe_02,

Did this just start happening with a recent Openfire update? What client are your users using?

I am trying to track down this potiential bug…

daryl

#5

We are using

Openfire

3.3.2

It seems like it has been going on for a while but only recently became a major problem with several of our clients having the problem.

We have a home grown app using the smack library to connect to the server.

Let me know if you need anything else.