Confluence doesn't start after upgrading from 7.1.0 to 7.12.2

[Fabián Olivera]

After receiving several "End life" warnings for some days I decided tu upgrade my Confluence (Server) from 7.1.0 to its latest version (7.12.2).  Everything seemed to be fine, and also the Windows service starts, but I only get "The service is unavailable." in my browser. 

I've been checking logs and I don't see anything relevant for such issue.

Could somebody give me some clues?

Thank you!

[Joshua Sneed Contegix]

Hi Fabian,

What error is posted to the logs when you attempt to start the app? Cheers!

[Fabián Olivera]

Hi!  Is there a way to attach logs here?  Sorry for my ignorance.

Here is what I get in the confluence-stderr file:

"2021-06-09 23:56:13 Apache Commons Daemon procrun stderr initialized.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy (file:/C:/Program%20Files/Atlassian/Confluence/confluence/WEB-INF/lib/hibernate.adapter-1.0.3.jar) to field java.lang.reflect.Field.modifiers
WARNING: Please consider reporting this to the maintainers of com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[debug] to [0]
09-Jun-2021 23:56:14.101 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine/Host/Context] failed to set property [debug] to [0]
09-Jun-2021 23:56:14.132 WARNING [main] org.apache.catalina.core.StandardContext.setPath A context path must either be an empty string or start with a '/' and do not end with a '/'. The path [${confluence.context.path}/synchrony-proxy] does not meet these criteria and has been changed to [/${confluence.context.path}/synchrony-proxy]
09-Jun-2021 23:56:14.132 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Engine/Host/Context] failed to set property [debug] to [0]
09-Jun-2021 23:56:14.788 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]
09-Jun-2021 23:56:14.913 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8010"]
09-Jun-2021 23:56:14.929 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1222] milliseconds
09-Jun-2021 23:56:14.929 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat-Standalone]
09-Jun-2021 23:56:14.929 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.45]
09-Jun-2021 23:56:18.726 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.
09-Jun-2021 23:56:19.367 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath
09-Jun-2021 23:56:19.945 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'
log4j:ERROR Could not find value for key log4j.appender.luceneQuery
log4j:ERROR Could not instantiate appender named "luceneQuery".
Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
10-Jun-2021 00:01:01.261 INFO [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying deployment descriptor [C:\Program Files\Atlassian\Confluence\conf\Standalone\localhost\synchrony-proxy.xml]
10-Jun-2021 00:01:01.277 WARNING [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployDescriptor The path attribute with value [/synchrony-proxy] in deployment descriptor [C:\Program Files\Atlassian\Confluence\conf\Standalone\localhost\synchrony-proxy.xml] has been ignored
10-Jun-2021 00:01:01.292 WARNING [Catalina-utility-1] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Context] failed to set property [debug] to [0]
10-Jun-2021 00:01:04.511 INFO [Catalina-utility-1] 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.
10-Jun-2021 00:01:05.511 INFO [Catalina-utility-1] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath
10-Jun-2021 00:01:06.027 INFO [Catalina-utility-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'
10-Jun-2021 00:01:09.389 INFO [Catalina-utility-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [C:\Program Files\Atlassian\Confluence\conf\Standalone\localhost\synchrony-proxy.xml] has finished in [8,094] ms
10-Jun-2021 00:01:09.389 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8090"]
10-Jun-2021 00:01:09.402 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-8010"]
10-Jun-2021 00:01:09.417 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [294494] milliseconds"

[Fabián Olivera]

The Confluence Windows Service is actually running, but it just doesn't work:

[Joshua Sneed Contegix]

Hi @Fabian,

It looks like the tomcat server is starting, but Confluence isn't served. This could be due to any number of reasons.

Start by reviewing/comparing supported platforms for your version against what you have installed. The next item to check would be file system ownership/permissions. Attempt to start if anything is found.

If that does not turn anything up; I would roll logs, restart, and look for ERRORs or FATALs. My guess is that you have an incorrect configuration in server.xml because I see context errors.

Cheers!