Confluence keeps spawning new Java processes that use 200% CPU under no load

Question

I have confluence installed on a virtual CentOS machine. It is currently a pretty bare-bone installation with no data and no users. However, Confluence keeps spawning new java processes that use nearly 200% (2 cores at 100%) before quitting. Once one of these processes has quit the next one starts.

You can find a screen recording of the top command, sorted by CPU usage here: https://www.dropbox.com/s/m61m2tyvlsvxpzh/Confluence%20200%20CPU.mov. I know that this is not much information to go on, but I’m very happy to provide more details as needed.

The problem exists both when running Confluence as a service (using sudo /etc/init.d/confluence start) as well as when starting confluence using start-confluence.sh.

Alex_Hoppen · Answer

It’s a bare bone install without any plugins. Also there is no suspicious log activity. I have attached the log of catalina.out of a full start up with the problem below:

06-Sep-2019 14:13:37.741 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server] failed to set property [debug] to [0]
06-Sep-2019 14:13:37.784 WARNING [main] org.apache.catalina.startup.SetAllPropertiesRule.begin [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.
06-Sep-2019 14:13:37.813 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine] failed to set property [debug] to [0]
06-Sep-2019 14:13:37.818 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine/Host] failed to set property [debug] to [0]
06-Sep-2019 14:13:37.841 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine/Host/Context] failed to set property [debug] to [0]
06-Sep-2019 14:13:37.855 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine/Host/Context] failed to set property [debug] to [0]
06-Sep-2019 14:13:38.052 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
06-Sep-2019 14:13:38.075 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio2-8091"]
06-Sep-2019 14:13:38.236 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [559] milliseconds
06-Sep-2019 14:13:38.243 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat-Standalone]
06-Sep-2019 14:13:38.243 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.22]
06-Sep-2019 14:13:39.292 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@7318ede4]
06-Sep-2019 14:13:39.364 INFO [Catalina-utility-2] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
06-Sep-2019 14:13:39.576 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'
06-Sep-2019 14:13:39.577 INFO [Catalina-utility-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started
06-Sep-2019 14:13:39.580 INFO [Catalina-utility-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Sep 06 14:13:39 CEST 2019]; root of context hierarchy
06-Sep-2019 14:13:39.629 INFO [Catalina-utility-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.loadBeanDefinitions Registering annotated classes: [class com.atlassian.synchrony.proxy.websocket.WebSocketConfig,class com.atlassian.synchrony.proxy.web.SynchronyWebMvcConfig]
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
2019-09-06 14:13:39,898 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.15.9 [build 8100 based on commit hash 5084f018d64a97dc638ca9a178856f851ea353ff] - synchrony version 2.1.0-release-confluence_6.15-32f7299a
06-Sep-2019 14:13:40.013 INFO [Catalina-utility-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'
06-Sep-2019 14:13:40.049 INFO [Catalina-utility-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/v1/bayeux-sync1] onto handler of type [class org.springframework.web.socket.server.support.WebSocketHttpRequestHandler]
06-Sep-2019 14:13:40.447 INFO [Catalina-utility-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/healthcheck]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()
06-Sep-2019 14:13:40.449 INFO [Catalina-utility-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{[/reload],methods=[PUT]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)
06-Sep-2019 14:13:40.473 INFO [Catalina-utility-2] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path [/**] onto handler of type [class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler]
06-Sep-2019 14:13:40.507 INFO [Catalina-utility-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Sep 06 14:13:39 CEST 2019]; root of context hierarchy
06-Sep-2019 14:13:40.631 INFO [Catalina-utility-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647
06-Sep-2019 14:13:40.653 INFO [Catalina-utility-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1076 ms

Daniel Wester _55 Degrees_ · Answer

Do you have any apps installed? Is there any log activity?