powered by Jive Software

Openfire server couldn't response


#1

Hey Team,

we are running openfire server version 4.0.2 since last 1 and half year in profduction and was working very fine upto yesterday. Now server couldn’t response to client and always terminate the connection of client and client no longer communicate with the server.

Configuration of server :slight_smile:

OS = ubuntu 16.04 (AMAZON EC2)
RAM = 32 GB
DB = Postgres SQL RDS

please let me know if you need any more inormation.

Please find the following log from the log file and suggest the solution if you have.

2018.12.20 18:20:19 WARN [HouseKeeper]: org.jivesoftware.util.log.util.CommonsLogFactory - #0627 was active for 328156 milliseconds and has been removed automaticaly. The Thread responsible was named ‘Thread-6182’, but the last SQL it performed is unknown because the trace property is not enabled.
2018.12.20 18:20:19 WARN [HouseKeeper]: org.jivesoftware.util.log.util.CommonsLogFactory - #0646 was active for 300407 milliseconds and has been removed automaticaly. The Thread responsible was named ‘Thread-6184’, but the last SQL it performed is unknown because the trace property is not enabled.
2018.12.20 18:20:19 WARN [HouseKeeper]: org.jivesoftware.util.log.util.CommonsLogFactory - #0645 was active for 302496 milliseconds and has been removed automaticaly. The Thread responsible was named ‘socket_c2s-thread-12’, but the last SQL it performed is unknown because the trace property is not enabled.
2018.12.20 18:20:19 WARN [HouseKeeper]: org.jivesoftware.util.log.util.CommonsLogFactory - #0646 was active for 300407 milliseconds and has been removed automaticaly. The Thread responsible was named ‘Thread-6184’, but the last SQL it performed is unknown because the trace property is not enabled.
2018.12.20 18:20:19 WARN [HouseKeeper]: org.jivesoftware.util.log.util.CommonsLogFactory - #0645 was active for 302496 milliseconds and has been removed automaticaly. The Thread responsible was named ‘socket_c2s-thread-12’, but the last SQL it performed is unknown because the trace property is not enabled.

2018.12.20 18:10:58 WARN [socket_c2s-thread-14]: org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to exception in session: (0x000411F4: nio socket, server, null => 0.0.0.0/0.0.0.0:5222)
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:197)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:202)
at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:42)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:620)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:598)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:587)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:61)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:969)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Thanks,
Hiren Vavadiya


#2

anyone having any comments on it ?