You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2021. It is now read-only.
Current implementation of msg.websocket creates new connection on AEM Author when the old one is disconnected (see SocketClientRunnablerun() method). It looks that those connections are not closed properly on AEM Author. After running AEM instance for 2 day I had over 800 threads like this:
10.03.2017 14:49:48.820 *ERROR* [FelixStartLevel] ERROR: Bundle '134' EventDispatcher: Error during dispatch. (java.lang.OutOfMemoryError: unable to create new native thread)
The default timeout for connection is 5 minutes and when the connection is idle for that time, connection breaks. A new connection is initiated on AEM Author then.
It looks that there is some problem with proper closing connections that were timed out:
AEM Publish log:
13.03.2017 14:58:19.865 *DEBUG* [qtp774165320-104] com.cognifide.actions.msg.websocket.servlet.MessageSocket Socket Error occured
java.net.SocketTimeoutException: Timeout on Read
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:545)
at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173)
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:510)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:586)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
The text was updated successfully, but these errors were encountered:
Current implementation of
msg.websocket
creates new connection on AEM Author when the old one is disconnected (seeSocketClientRunnable
run()
method). It looks that those connections are not closed properly on AEM Author. After running AEM instance for 2 day I had over 800 threads like this:After some time I get:
The default timeout for connection is 5 minutes and when the connection is idle for that time, connection breaks. A new connection is initiated on AEM Author then.
It looks that there is some problem with proper closing connections that were timed out:
AEM Publish log:
The text was updated successfully, but these errors were encountered: