C3P0Registry mbean is not being unregistered during shutdown

XMLWordPrintable

    • 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.

            Assignee:
            Steve Haffenden (Inactive)
            Reporter:
            Igor Minar
            Votes:
            3 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: