I got tons of these JavaExeptions in my confluence logs. And have to reboot the server once per day.

Kosta February 8, 2019
Can any one tell me where to look for the cause of this problems?


07-Feb-2019 19:59:05.320 SEVERE [http-nio-8090-exec-122] org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed Unhandled error for ExceptionWebSocketHandlerDecorator [delegate=LoggingWebSocketHandlerDecorator [delegate=PerConnectionWebSocketHandlerProxy[handlerType=class com.atlassian.synchrony.proxy.websocket.WebSocketProxy]]]
 java.util.concurrent.TimeoutException
        at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
        at com.atlassian.synchrony.proxy.websocket.WebSocketUpstreamHandler.getSynchronySession(WebSocketUpstreamHandler.java:64)
        at com.atlassian.synchrony.proxy.websocket.WebSocketProxy.tryCloseRemoteSession(WebSocketProxy.java:94)
        at com.atlassian.synchrony.proxy.websocket.WebSocketProxy.afterConnectionClosed(WebSocketProxy.java:78)
        at org.springframework.web.socket.handler.PerConnectionWebSocketHandler.afterConnectionClosed(PerConnectionWebSocketHandler.java:97)
        at org.springframework.web.socket.handler.WebSocketHandlerDecorator.afterConnectionClosed(WebSocketHandlerDecorator.java:85)
        at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.afterConnectionClosed(LoggingWebSocketHandlerDecorator.java:72)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed(ExceptionWebSocketHandlerDecorator.java:78)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onClose(StandardWebSocketHandlerAdapter.java:141)
        at org.apache.tomcat.websocket.WsSession.fireEndpointOnClose(WsSession.java:535)
        at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:481)
        at org.apache.tomcat.websocket.WsSession.close(WsSession.java:445)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:217)
        at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:140)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.tryCloseWithError(ExceptionWebSocketHandlerDecorator.java:94)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionEstablished(ExceptionWebSocketHandlerDecorator.java:51)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onOpen(StandardWebSocketHandlerAdapter.java:100)
        at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init(WsHttpUpgradeHandler.java:133)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:816)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:748)

07-Feb-2019 19:59:54.469 SEVERE [http-nio-8090-exec-118] org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed Unhandled error for ExceptionWebSocketHandlerDecorator [delegate=LoggingWebSocketHandlerDecorator [delegate=PerConnectionWebSocketHandlerProxy[handlerType=class com.atlassian.synchrony.proxy.websocket.WebSocketProxy]]]
 java.util.concurrent.TimeoutException
        at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1771)
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
        at com.atlassian.synchrony.proxy.websocket.WebSocketUpstreamHandler.getSynchronySession(WebSocketUpstreamHandler.java:64)
        at com.atlassian.synchrony.proxy.websocket.WebSocketProxy.tryCloseRemoteSession(WebSocketProxy.java:94)
        at com.atlassian.synchrony.proxy.websocket.WebSocketProxy.afterConnectionClosed(WebSocketProxy.java:78)
        at org.springframework.web.socket.handler.PerConnectionWebSocketHandler.afterConnectionClosed(PerConnectionWebSocketHandler.java:97)
        at org.springframework.web.socket.handler.WebSocketHandlerDecorator.afterConnectionClosed(WebSocketHandlerDecorator.java:85)
        at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.afterConnectionClosed(LoggingWebSocketHandlerDecorator.java:72)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed(ExceptionWebSocketHandlerDecorator.java:78)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onClose(StandardWebSocketHandlerAdapter.java:141)
        at org.apache.tomcat.websocket.WsSession.fireEndpointOnClose(WsSession.java:535)
        at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:481)
        at org.apache.tomcat.websocket.WsSession.close(WsSession.java:445)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:217)
        at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:140)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.tryCloseWithError(ExceptionWebSocketHandlerDecorator.java:94)
        at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionEstablished(ExceptionWebSocketHandlerDecorator.java:51)
        at org.springframework.web.socket.adapter.standard.StandardWebSocketHandlerAdapter.onOpen(StandardWebSocketHandlerAdapter.java:100)
        at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init(WsHttpUpgradeHandler.java:133)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:816)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:748)

2 answers

0 votes
Michael Hayden
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 15, 2019

We also experienced this on our environment. We had Collaborative Editing turned on, but were not able to edit nor create pages, so we turned it off.  We continued to get these errors.  After a bit of digging, it seemed to stem back to when we were doing an automatic backup of the system.  The environment ran out of memory whilst doing the backup. At the same time, the websocket tried to connect, and because the system had run out of memory, that job failed.  The websocket connection then appeared to get itself in a loop of trying to connect and subsequently failing.  This was not resolved by restarting the confluence instance as there must have been a rogue process running.  We rebooted the box confluence is running on, turned on Collaborative Editing, and all now appears to be well.  

0 votes
Diego
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 11, 2019

Hello there! Thanks for sharing with the Community Konstantinos.

Other than this error in your logs, are is there any kind of problems with your instance:

  1. Are you able to edit Confluence pages?
  2. Are you able to create new pages?
  3. Are you able to navigate within the instance?
  4. Does the instance lock up when those errors come up in the logs?
  5. When did you first notice these errors?
  6. Have you applied any kind of change prior to this issue?
  7. Are you using a proxy between Confluence and the hosts?
  8. Is there a firewall?
  9. Is this issue present at a specific time of the day or is it random?
  10. How much memory is allocated for Confluence?
  11. Is this a newly installed instance?

If you are facing problems while editing pages, you could take a look at this article here:

Confluence throws "The editor didn't load this time" error when trying to edit a page

Let us know!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events