When starting up Tomcat (6.0.26 or higher), the log file reports that Catalina started with no issues:
When shutting down Tomcat, Catalina reports multiple threads have failed to stop:
There is a memory leak detection feature introduced in Tomcat 6.0.25 that attempts to log objects that have failed to be unregistered by webapps it hosts when they are stopped, and were forcibly unregistered by Tomcat. As Tomcat is forcibly removing these objects, it is not a serious concern that these log messages occur.
These errors will also appear during startup if your JDBC driver is not in the correct location on startup. If you are using a datasource, be sure to copy the JDBC drive to
<confluence-install>/lib. If the issue persists, verify that you are able to authenticate against your database with the credentials supplied in your
<confluence-home>/confluence.cfg.xml in the Hibernate connection settings.
Despite their apparent severity, these log messages are benign and can be safely ignored.
There is no resolution at this time. There is an improvement request to reduce these harmless messages in the log during Confluence shutdown, which is being tracked at CONF-22879 - Reduce errors logged when shutting down Confluence Open .
This workaround is not recommended as Tomcat 6.0.20 has known performance issues, and has several security vulnerabilities. We recommend customers upgrade to (or continue to run) Tomcat 6.0.32 or higher.