Error when starts tomcat (Confluence 3.5.17 and 4.2.8)
Asked by Pedro Sousa:

I'm writing a class that extends the class of authentication to Confluence integration with a service used to authenticate users in Confluence, but when I realize deploy the jars and modify the seraph.config to use the class I wrote the beginning and tomcat, this is what happens the following error

```
23/08/2012 15:19:48 org.apache.tomcat.util.digester.SetPropertiesRule beginAVISO: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not finda matching property.23/08/2012 15:19:48 org.apache.tomcat.util.digester.SetPropertiesRule beginAVISO: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.23/08/2012 15:19:48 org.apache.tomcat.util.digester.SetPropertiesRule beginAVISO: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug'to '0' did not find a matching property.23/08/2012 15:19:48 org.apache.tomcat.util.digester.SetPropertiesRule beginAVISO: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property'debug' to '0' did not find a matching property.23/08/2012 15:19:48 org.apache.coyote.http11.Http11Protocol initINFO: Initializing Coyote HTTP/1.1 on http-808023/08/2012 15:19:48 org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 208 ms23/08/2012 15:19:48 org.apache.catalina.core.StandardService startINFO: Starting service Tomcat-Standalone23/08/2012 15:19:48 org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.322012-08-23 15:19:51,207 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 3.5.17 (build #2176)2012-08-23 15:19:58,472 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system2012-08-23 15:19:58,613 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Plugin system started in 0:00:00.1412012-08-23 15:19:59,379 WARN [main] [atlassian.config.xml.AbstractDom4jXmlConfigurationPersister] saveDocumentAtomically Unable to move D:\Documents and Settings\y6fk\Desktop\Migra??oConfluence\data\confluence.cfg.xml4103963291859695066tmpto D:\Documents and Settings\y6fk\Desktop\Migra??oConfluence\data\confluence.cfg.xml. Falling back to non-atomic overwrite.23/08/2012 15:20:08 org.apache.catalina.core.StandardContext startGRAVE: Error listenerStart23/08/2012 15:20:08 org.apache.catalina.core.StandardContext startGRAVE: Context [] startup failed due to previous errors23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcGRAVE: The web application [] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent amemory leak, the JDBC Driver has been forcibly unregistered.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcGRAVE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent amemory leak, the JDBC Driver has been forcibly unregistered.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: The web application [] appears to have started a thread named [HSQLDB Timer @1544e44] but has failed to stop it. This is very likely to create a memory leak.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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 likelyto create a memory leak.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsGRAVE: 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.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMapGRAVE: The web application [] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@100e398]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@15e10ab]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMapGRAVE: The web application [] created a ThreadLocal with key of type [com.atlassian.core.logging.ThreadLocalErrorCollection$2] (value [com.atlassian.core.logging.ThreadLocalErrorCollection$2@987c7d]) 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.23/08/2012 15:20:09 org.apache.coyote.http11.Http11Protocol startINFO: Starting Coyote HTTP/1.1 on http-808023/08/2012 15:20:09 org.apache.catalina.startup.Catalina startINFO: Server startup in 20404 msException in thread "HSQLDB Timer @1544e44" java.lang.NullPointerException        at org.hsqldb.lib.HsqlTimer.nextTask(HsqlTimer.java:512)        at org.hsqldb.lib.HsqlTimer$TaskRunner.run(HsqlTimer.java:611)        at java.lang.Thread.run(Thread.java:662)
```

The same happens in version 4.2.8. Anyone know what can be?

<br />


Answers:
author: Amalia
body: It seems that you are using HSQLDB as mentioned in the error. Please try using one of the [supported external databases](https://confluence.atlassian.com/display/DOC/Supported+Platforms) and see if the error persists.

comments: author: Pedro Sousa
body: Amalia

The problem was the embedded database, I set to External Database and runs ok