Xmpp.client.idle not working

Openfire Openfire Support
1

Hi folks,

We just upgraded to openfire 3.5.1. Now xmpp.client.idle = -1 doesn’t seem to be working. Our users keep getting kicked. Wondering if there was some new setting change we needed to be aware of or something.

-Walt

2

Hi Walt,

I ran into something similiar. What client are your folks using?

Also, if you put Openfire into debug mode, does it list the reason why users are getting kicked?

daryl

3

Hi all,

I also got this issue. In the debug log, i often found this exception, is this something related?

2008.06.20 06:17:37 JettyLog: EXCEPTION

java.io.IOException: Connection reset by peer

at sun.nio.ch.FileDispatcher.read0(Native Method)

at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)

at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)

at sun.nio.ch.IOUtil.read(IOUtil.java:206)

at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)

at org.mortbay.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:122)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:282)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)

at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

2008.06.20 06:17:37 JettyLog: EOF

Thanks.

From BillChan.

4

I noticed that the xmpp.client.idle does not always work as well…sometimes it works and sometimes it doesn’t. why is that I am using 3.6.3.