Help! Users getting kicked off Openfire server, debug logs inside

Openfire Openfire Support
1

Hi All,

We’re running Openfire 3.4.2 as our jabber server for a small development team. We’re using Pandion 2.5 as the chat clients. We were running an older version of the wildfire server and needed to transition the server to a new machine so we upgraded from wildfire to openfire. Unfortunuately, immediately after the upgrade, and with no changes to the client software, users started randomly getting disconnected from the server. I turned on the Debug log inside the openfire admin console and have pasted in a relevant section. Any assitance with this would be GREATLY appreciate!

The user referenced below wasn’t even at his desk when he was disconnected and then reconnected.

2007.12.21 10:30:38 JettyLog: EXCEPTION

java.io.IOException: An existing connection was forcibly closed by the remote host

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

at sun.nio.ch.SocketDispatcher.read(Unknown Source)

at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)

at sun.nio.ch.IOUtil.read(Unknown Source)

at sun.nio.ch.SocketChannelImpl.read(Unknown Source)

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

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:381)

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

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

2007.12.21 10:30:38 JettyLog: EOF

2007.12.21 10:34:21 XMPPCallbackHandler: RealmCallback: dummy

2007.12.21 10:34:21 XMPPCallbackHandler: NameCallback: mikes

2007.12.21 10:34:21 XMPPCallbackHandler: PasswordCallback

2007.12.21 10:34:21 XMPPCallbackHandler: AuthorizeCallback

2007.12.21 10:34:21 AuthorizationManager: Trying Default Mapping.map(mikes)

2007.12.21 10:34:21 DefaultAuthorizationMapping: No realm found

2007.12.21 10:34:21 XMPPCallbackHandler: no username requested, using mikes

2007.12.21 10:34:21 AuthorizationManager: Trying Default Policy.authorize(mikes , mikes)

2007.12.21 10:34:21 DefaultAuthorizationPolicy: Checking authenID realm

2007.12.21 10:34:21 XMPPCallbackHandler: mikes authorized to mikes

2

Hey Mike,

I don’t think that exception is related to users being disconnected. The stack trace of that errors shows that the disconnection happened to someone using a browser probably when using the admin console.

I don’t know how you made the upgrade to 3.4.2. If you are using an old plugin you might get this problem so try removing all plugins and see if the problem happens. This problem could also be related to idle timeouts. The server will disconnect connections that have not been sending any traffic to the servers. Usually clients send hearbeats to the server every 30 seconds to keep the connection alive. You can set the system property xmpp.client.idle from the admin console to a very high value and see if the problem still happens. The value of that property is in milliseconds. Once you made the change new connections will start using the new value so you might want to restart the server to be sure that all sessions are using the new value.

Regards,

– Gato