Error when starts tomcat (Confluence 3.5.17 and 4.2.8)

[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 begin
AVISO: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find
a matching property.
23/08/2012 15:19:48 org.apache.tomcat.util.digester.SetPropertiesRule begin
AVISO: [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 begin
AVISO: [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 begin
AVISO: [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 init
INFO: Initializing Coyote HTTP/1.1 on http-8080
23/08/2012 15:19:48 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 208 ms
23/08/2012 15:19:48 org.apache.catalina.core.StandardService start
INFO: Starting service Tomcat-Standalone
23/08/2012 15:19:48 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
2012-08-23 15:19:51,207 INFO [main] [com.atlassian.confluence.lifecycle] context
Initialized Starting Confluence 3.5.17 (build #2176)
2012-08-23 15:19:58,472 INFO [main] [atlassian.plugin.manager.DefaultPluginManag
er] init Initialising the plugin system
2012-08-23 15:19:58,613 INFO [main] [atlassian.plugin.manager.DefaultPluginManag
er] init Plugin system started in 0:00:00.141
2012-08-23 15:19:59,379 WARN [main] [atlassian.config.xml.AbstractDom4jXmlConfig
urationPersister] saveDocumentAtomically Unable to move D:\Documents and Setting
s\y6fk\Desktop\MigraþÒoConfluence\data\confluence.cfg.xml4103963291859695066tmp
to 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 start
GRAVE: Error listenerStart
23/08/2012 15:20:08 org.apache.catalina.core.StandardContext start
GRAVE: Context [] startup failed due to previous errors
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Jdbc
GRAVE: 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.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Jdbc
GRAVE: 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.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Jdbc
GRAVE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDr
iver] but failed to unregister it when the web application was stopped. To preve
nt a memory leak, the JDBC Driver has been forcibly unregistered.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [HSQLDB Tim
er @1544e44] but has failed to stop it. This is very likely to create a memory l
eak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: 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.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-1] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-2] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-3] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-4] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-5] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-6] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-7] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-8] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-9] but has failed to stop it. This is very likely to create a memor
y leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearReferences
Threads
GRAVE: The web application [] appears to have started a thread named [QuartzSche
duler_Worker-10] but has failed to stop it. This is very likely to create a memo
ry leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearThreadLoca
lMap
GRAVE: The web application [] created a ThreadLocal with key of type [java.lang.
ThreadLocal] (value [java.lang.ThreadLocal@100e398]) and a value of type [org.do
m4j.DocumentFactory] (value [org.dom4j.DocumentFactory@15e10ab]) but failed to r
emove it when the web application was stopped. This is very likely to create a m
emory leak.
23/08/2012 15:20:08 org.apache.catalina.loader.WebappClassLoader clearThreadLoca
lMap
GRAVE: The web application [] created a ThreadLocal with key of type [com.atlass
ian.core.logging.ThreadLocalErrorCollection$2] (value [com.atlassian.core.loggin
g.ThreadLocalErrorCollection$2@987c7d]) and a value of type [java.lang.Boolean]
(value [false]) but failed to remove it when the web application was stopped. Th
is is very likely to create a memory leak.
23/08/2012 15:20:09 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
23/08/2012 15:20:09 org.apache.catalina.startup.Catalina start
INFO: Server startup in 20404 ms
Exception 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?

[Amalia · Accepted solution]

It seems that you are using HSQLDB as mentioned in the error. Please try using one of the supported external databases and see if the error persists.

[Pedro Sousa]

Amalia

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