Hello,
Our Confluence version is 6.10.1.
The Confluence page cannot be loaded suddenly. Finally, the 503 error code is displayed on the page. We checked the server and the process is still running. Then we checked the catalina.out log and atlassian-confluence.log and found OutOfMemory error.
catalina.out log:
18-Sep-2018 14:49:42.938 WARNING [Finalizer] org.apache.tomcat.util.net.NioBlockingSelector$KeyReference.finalize Possible key leak, cancelling key in the finalizer.
Exception in thread "https-jsse-nio-8443-Acceptor-0" Exception in thread "https-jsse-nio-8443-exec-10" Exception in thread "C3P0PooledConnectionPoolManager[identityToken->z8kflt9w1xjj49spkan33|3d8d19af]-AdminTaskTimer" Exception in thread "https-jsse-nio-8443-exec-18" Exception in thread "C3P0PooledConnectionPoolManager[identityToken->z8kflt9w1xjj49spkan33|4a1dd9e2]-AdminTaskTimer" Exception in thread "https-jsse-nio-8443-exec-4" Exception in thread "https-jsse-nio-8443-exec-22" Exception in thread "https-jsse-nio-8443-exec-7" Exception in thread "https-jsse-nio-8443-exec-12" Exception in thread "https-jsse-nio-8443-exec-1" Exception in thread "https-jsse-nio-8443-exec-13" java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
atlassian-confluence.log
2018-09-18 14:49:42,982 ERROR [https-jsse-nio-8443-exec-41] [[Standalone].[localhost].[/].[action]] log Servlet.service() for servlet [action] in context with path [] threw exception
java.lang.RuntimeException: javax.servlet.ServletException: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getConfluenceResourceTags' in class com.atlassian.confluence.setup.velocity.VelocityFriendlyPageBuilderService threw exception java.lang.OutOfMemoryError: Java heap space at /decorators/includes/header.vm[line 90, column 24]
Finally, we restarted the confluence service and the page access returned to normal. After that, we checked the monitoring records and found that the confluence has keeped many http sessions, and the heap memory had been occupied a lot (about more than 8G).
Is this problem caused by the http session not ending properly and the memory not being released?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.