Upgrade From 4.1.3 to 4.1.10 Failing, Logs Not Helpful

[Scott Vieth]

I am attempting to upgrade our DEV environment of Confluence from 4.1.3 to 4.1.10. We use a MSSQL server and rely on our production JIRA server for authentication. Because of that, I have migrated all of the necessary settings for the Confluence home directory, the osuser file, and the server.xml file to the new directory.

However, when it starts up, the new version that is, the startup is much faster, about 30 seconds compared to a couple of minutes, and doesn't appear to do much. Navigating to the web page leaves me with a message saying:

Upgrade failed. Please consult the system logs for details. You will need to fix these problems, restore your database and confluence home directory to the pre upgrade state. Then retry the upgrade.

The only log file that had entries in it was the Catalina one, and it wasn't terribly helpful:

May 21, 2012 11:26:58 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

May 21, 2012 11:26:58 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

May 21, 2012 11:26:58 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.

May 21, 2012 11:26:58 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.

May 21, 2012 11:26:58 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8081

May 21, 2012 11:26:58 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 301 ms

May 21, 2012 11:26:58 AM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

May 21, 2012 11:26:58 AM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

May 21, 2012 11:27:19 AM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8081

May 21, 2012 11:27:19 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 20162 ms

May 21, 2012 11:27:29 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8081

May 21, 2012 11:27:30 AM org.apache.catalina.core.StandardService stop

INFO: Stopping service Tomcat-Standalone

May 21, 2012 11:27:30 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.

May 21, 2012 11:27:30 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.

May 21, 2012 11:27:30 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.

May 21, 2012 11:27:30 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver net.sourceforge.jtds.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 21, 2012 11:27:30 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@ebf00e ) 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.

May 21, 2012 11:27:30 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@1dd58d8 ) and a value of type org.dom4j.DocumentFactory (value org.dom4j.DocumentFactory@f3de46 ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

May 21, 2012 11:27:30 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.opensymphony.xwork.ActionContext.ActionContextThreadLocal (value com.opensymphony.xwork.ActionContext$ActionContextThreadLocal@5009ea ) and a value of type com.opensymphony.xwork.ActionContext (value com.opensymphony.xwork.ActionContext@bae5e9 ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

May 21, 2012 11:27:31 AM org.apache.coyote.http11.Http11Protocol destroy

INFO: Stopping Coyote HTTP/1.1 on http-8081

Not a lot there I can get to tell me exactly why it failed. It's as if the HTTP Daemon starts up correctly but it never gets around to seeing the database to do the upgrade process (running the 4.1.3 standalone process works perfectly).

Any thoughts as to what I might be missing here? Thanks!

[Azwandi Mohd Aris]

Instead of catalina.out, you need to find the atlassian-confluence.log, which should contain more detailed information about the error message. This file can be found in your <confluence-home>/logs directory (do not confuse this with <confluence-installation>/logs directory. See this page for detailed instructions to find the log.