Confluence test instance will not start correctly

I have taken an image of our production instance and followed this document:
http://confluence.atlassian.com/display/DOC/Migrating+Confluence+Between+Servers

confluence seems to start but with a number of errors in the log similar to:
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.

This article seems to suggest this is not serious:
https://jira.atlassian.com/browse/CONF-22879

I have followed http://confluence.atlassian.com/display/DOC/Troubleshooting+External+Database+Connections and this confirmed that tomcat was able to connect to the db with no problem

however when trying to access https://173.203.237.62/ I still receive
http status 404
The requested resource is not available.

what do I need to do to get this test environment functioning?

please see below for log entries during a start up:

Mar 16, 2012 12:00:03 PM org.apache.catalina.core.StandardService stop

INFO: Stopping service Tomcat-Standalone

Mar 16, 2012 12:00:03 PM org.apache.catalina.core.StandardContext stop

INFO: Container org.apache.catalina.core.ContainerBase.[Standalone].[localhost].[/] has not been started

Mar 16, 2012 12:00:24 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

Mar 16, 2012 12:00:25 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

Mar 16, 2012 12:00:25 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

Mar 16, 2012 12:00:25 PM 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.

Mar 16, 2012 12:00:25 PM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 380 ms

Mar 16, 2012 12:00:25 PM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

Mar 16, 2012 12:00:25 PM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-03-16 12:00:30,204 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 3.5.9 (build #2166)

2012-03-16 12:00:33,973 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system

2012-03-16 12:00:34,207 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Plugin system started in 0:00:00.231

Mar 16, 2012 12:00:52 PM org.apache.catalina.core.StandardContext start

SEVERE: Error listenerStart

Mar 16, 2012 12:00:52 PM org.apache.catalina.core.StandardContext start

SEVERE: Context [] startup failed due to previous errors

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

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

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM 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.

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [] created a ThreadLocal with key of type [com.atlassian.confluence.concurrent.ThreadLocalMap] (value [com.atlassian.confluence.concurrent.ThreadLocalMap@32df8508]) and a value of type [java.util.HashMap] (value [{}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Mar 16, 2012 12:00:52 PM 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@43f12248]) 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.

Mar 16, 2012 12:00:52 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@c01c7d1]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@48e5707f]) 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.

Mar 16, 2012 12:00:53 PM org.apache.jk.common.ChannelSocket init

INFO: JK: ajp13 listening on /127.0.0.1:8080

Mar 16, 2012 12:00:53 PM org.apache.jk.server.JkMain start

INFO: Jk running ID=0 time=0/25 config=null

Mar 16, 2012 12:00:53 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 28597 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)

4 answers

Were you able to start up the new confluence without your data? (barebones system)

Are you positive that the migration is using the same version of Confluence?

I am also having the same issue. Did you find a solution to this problem?

It turned out that the problem was down to a failed database copy. a database had been created but contained no data. Once this was resolved there were no problems

I have this exact same problem, however this has occured after starting confluence up after a power failure. Does this hint at a corrupt database and am I having to resolve to a backup in order to get this working?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

450 views 21 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you