Confluence server fails to restart after a power failure.
Asked by Troy Tarrant:

Nothing has changed in the environment, however restarting after a power failure I get a 404 status from Apache 6.0.32.

The following log trace hints at a JDBC Driver issue?

Jun 1, 2012 11:11:40 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server} Setting property 'debug' to '0' did not find a matching property.

Jun 1, 2012 11:11:40 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

Jun 1, 2012 11:11:40 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.

Jun 1, 2012 11:11:40 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.

Jun 1, 2012 11:11:40 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8090

Jun 1, 2012 11:11:40 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 384 ms

Jun 1, 2012 11:11:40 AM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

Jun 1, 2012 11:11:40 AM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-06-01 11:11:42,375 INFO main com.atlassian.confluence.lifecycle contextInitialized Starting Confluence 4.0 (build #3047)

Jun 1, 2012 11:12:33 AM org.apache.catalina.core.StandardContext start

SEVERE: Error listenerStart

Jun 1, 2012 11:12:33 AM org.apache.catalina.core.StandardContext start

SEVERE: Context startup failed due to previous errors

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.hsqldb.jdbc.JDBCDriver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.postgresql.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver com.mysql.jdbc.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Poller SunPKCS11-Darwin but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-1 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-2 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-3 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-4 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-5 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-6 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named scheduler_Worker-7 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.google.common.base.internal.Finalizer but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Timer-3 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Timer-4 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2 but has failed to stop it. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type java.lang.ThreadLocal (value java.lang.ThreadLocal@1bda6c0d ) and a value of type org.dom4j.DocumentFactory (value org.dom4j.DocumentFactory@20ebd7c4 ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Jun 1, 2012 11:12:34 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.atlassian.core.logging.ThreadLocalErrorCollection$2 (value com.atlassian.core.logging.ThreadLocalErrorCollection$2@f151bf2 ) and a value of type java.lang.Boolean (value false ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.

Jun 1, 2012 11:12:35 AM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8090

Jun 1, 2012 11:12:35 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 55278 ms

Exception in thread Timer-3 java.lang.NullPointerException

at com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.isLoggable(Log4jMLog.java:257)

at com.mchange.v2.resourcepool.BasicResourcePool$CullTask.run(BasicResourcePool.java:1934)

at java.util.TimerThread.mainLoop(Timer.java:512)

at java.util.TimerThread.run(Timer.java:462)

Exception in thread Timer-4 java.lang.NullPointerException

at com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.isLoggable(Log4jMLog.java:257)

at com.mchange.v2.resourcepool.BasicResourcePool$CullTask.run(BasicResourcePool.java:1934)

at java.util.TimerThread.mainLoop(Timer.java:512)

at java.util.TimerThread.run(Timer.java:462)

What do I need to do to resolve this?


Answers:
author: Scott Mercer
body: I am having a similar issue - did you ever find a solution?