-
Suggestion
-
Resolution: Low Engagement
-
None
-
1
-
21
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
In Tomcat 6.0.32, I get the following errors when shutting down Confluence, even after CONF-21385 is resolved:
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/confluence] 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.
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/confluence] 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.
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/confluence] 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.
2011-07-12 10:37:59,842 INFO [main] [com.atlassian.confluence.lifecycle] contextDestroyed Stopping Confluence
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/confluence] 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.
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of type [com.atlassian.core.logging.ThreadLocalErrorCollection$2] (value [com.atlassian.core.logging.ThreadLocalErrorCollection$2@2dc4df0b]) 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.
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@580f62a6]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@5a15ad74]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Jul 12, 2011 10:37:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of type [com.atlassian.confluence.concurrent.ThreadLocalMap] (value [com.atlassian.confluence.concurrent.ThreadLocalMap@452ec8e0]) and a value of type [java.util.HashMap] (value [{}]) 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.
Jul 12, 2011 10:38:00 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Disconnected from server
Those "SEVERE" and "ERROR" lines ideally wouldn't be there. It's Tomcat pointing out how some of our code and some of our library code doesn't clean up resources properly.
There's also a race condition in C3P0 that leads to error messages like this at shutdown:
Exception in thread "Timer-0" java.lang.NullPointerException at com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.isLoggable(Log4jMLog.java:257) at com.mchange.v2.resourcepool.BasicResourcePool$CheckIdleResourcesTask.run(BasicResourcePool.java:1961) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)
- is related to
-
- Closed
-
- Gathering Interest
[CONFCLOUD-22879] Reduce errors logged when shutting down Confluence
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server api&platform log-cleanup logging pse-request tomcat | New: affects-server api&platform cll-tf3202505 log-cleanup logging pse-request tomcat |
| Support reference count | Original: 20 | New: 21 |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Workflow | Original: JAC Suggestion Workflow [ 3428215 ] | New: JAC Suggestion Workflow 3 [ 3611138 ] |
| Workflow | Original: Confluence Workflow - Public Facing v3 [ 2239576 ] | New: JAC Suggestion Workflow [ 3428215 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Support reference count | New: 20 |
Hi everyone,
Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.
In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management