Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Errors in cataling.out log confluence can't set it up to work.

Isaac Montes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 25, 2012

----------This was the start up log--------------------

INFO: Initialization processed in 614 ms

May 25, 2012 7:47:15 PM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

May 25, 2012 7:47:15 PM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-05-25 19:47:17,624 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 4.2.3 (build #3280)

May 25, 2012 7:47:28 PM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8090

May 25, 2012 7:47:28 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 13518 ms

----------This this is the log when I stop it-------------------

May 25, 2012 8:00:12 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8090
May 25, 2012 8:00:13 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Tomcat-Standalone
May 25, 2012 8:00:13 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.
May 25, 2012 8:00:13 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.
May 25, 2012 8:00:13 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.
May 25, 2012 8:00:13 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@63b34ca]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@1906bcf8]) 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.
May 25, 2012 8:00:14 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8090
May 25, 2012 8:00:44 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
May 25, 2012 8:00:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
May 25, 2012 8:00:45 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.
May 25, 2012 8:00:45 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.

1 answer

1 accepted

2 votes
Answer accepted
Colin Goudie
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 25, 2012

I don't believe these are major issues. The errors on shutdown are to do with the deregistration of the JDBC drivers. Some info from SO

http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-jdbc-driver-has-been-forcibly-unregistered

TBH I have ignored these in installations myself but I'm interested to know if others have a better solution to :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events