Confluence won't start after upgrade from 6.5.1 to 6.15.2
Asked by Tuan Vo:

I have a working Confluence version 6.5.1 and wanted to upgrade to the latest version, 6.15.2. I have Confluence hosted in AWS on a Centos 7 node connected to an RDS Postgres DB.

I followed the pre steps for upgrading and everything was in order. However, after the upgrade, Confluence's status is active (exited).

Not sure what the issue is and was hoping someone with more knowledge on Confluence can help me out. Thank you.

Catalina logs below:

23-Apr-2019 16:07:46.683 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]

23-Apr-2019 16:07:46.694 INFO \[main\] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read

23-Apr-2019 16:07:46.699 INFO \[main\] org.apache.catalina.startup.Catalina.load Initialization processed in 554 ms

23-Apr-2019 16:07:46.706 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]

23-Apr-2019 16:07:46.706 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/9.0.12

23-Apr-2019 16:07:47.888 INFO \[localhost-startStop-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.

23-Apr-2019 16:07:48.047 INFO \[localhost-startStop-2\] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: \[com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@3b412f1\]

23-Apr-2019 16:07:48.216 INFO \[localhost-startStop-2\] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'

23-Apr-2019 16:07:48.216 INFO \[localhost-startStop-2\] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started

23-Apr-2019 16:07:48.222 INFO \[localhost-startStop-2\] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date \[Tue Apr 23 16:07:48 UTC 2019\]; root of context hierarchy

23-Apr-2019 16:07:48.264 INFO \[localhost-startStop-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\]

23-Apr-2019 16:07:48.708 INFO \[localhost-startStop-2\] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'

23-Apr-2019 16:07:48.739 INFO \[localhost-startStop-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\]

23-Apr-2019 16:07:49.020 INFO \[localhost-startStop-2\] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path \[/\*\*\] onto handler of type \[class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler\]

23-Apr-2019 16:07:49.083 INFO \[localhost-startStop-2\] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date \[Tue Apr 23 16:07:48 UTC 2019\]; root of context hierarchy

23-Apr-2019 16:07:49.148 INFO \[localhost-startStop-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()

23-Apr-2019 16:07:49.149 INFO \[localhost-startStop-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)

23-Apr-2019 16:07:49.212 INFO \[localhost-startStop-2\] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647

23-Apr-2019 16:07:49.233 INFO \[localhost-startStop-2\] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1017 ms

2019-04-23 16:07:50,497 INFO \[localhost-startStop-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 6.15.2 \[build 8100 based on commit hash 4410012ac87e845516b70bc69b6f7a893eabaa5a\] - synchrony version 2.1.0-master-9d112c9d


Answers:
author: Persis IT
body: Hi,

we have the same Problem. Please take notice of this issue und help us solve it.

Thanks in advance.

Regards

A.Nessak


Tags: confluence-server

server