-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
2.8.1, 2.8.2
-
None
-
9
-
This is a similar issue to http://jira.atlassian.com/browse/CONF-11534
If I deploy a new version or a new build of confluence to an app server without a restart, I always get this error:
WARN 2008-07-31 09:46:18,611 [service-j2ee-19] ActiveManagementCoordinator:attemptManageC3P0Registry - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources. erver.init.J2EERunner.confPostInit(J2EERunner.java:304)
This is pretty annoying on production servers, and even more annoying during development.
PS: You should create a compontent called "JMX" in this JIRA project, since a suitable place to file these reports does not exist.
Hi igorminar
Thanks for taking the time to raise this issue. This has been on our backlog now for 6 years with very little movement in that time, rather than leaving this here I'm going to close this out as won't fix I believe that this better reflects the status of the ticket.
If the problem is raised again in the future we'll readdress it.
Regards
Steve Haffenden
Confluence Bugmaster
Atlassian