Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-12645

C3P0Registry mbean is not being unregistered during shutdown

      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.

            [CONFSERVER-12645] C3P0Registry mbean is not being unregistered during shutdown

            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

            Steve Haffenden (Inactive) added a comment - 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

            Anatoli added a comment -

            updated the description - removed the part that is caused by CONF-11555

            Anatoli added a comment - updated the description - removed the part that is caused by CONF-11555

            Anatoli added a comment -

            Hi Greg,

            As Andrew has explained above

            the registration of the c3p0 MBean is actually done within c3p0 itself and we have no control over this behavior.

            The stacktrace that listed in the description however is caused by CONF-11555, which is already fixed.

            Anatoli.

            Anatoli added a comment - Hi Greg, As Andrew has explained above the registration of the c3p0 MBean is actually done within c3p0 itself and we have no control over this behavior. The stacktrace that listed in the description however is caused by CONF-11555 , which is already fixed. Anatoli.

            Greg Osuri added a comment -

            I'm getting the same issue. Any update on this?

            Greg Osuri added a comment - I'm getting the same issue. Any update on this?

            Igor, the registration of the c3p0 MBean is actually done within c3p0 itself and we have no control over this behavior.

            What you can do is specify the following system property:

            -Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
            

            to prevent c3p0 from registering its MBean.

            The actual stack trace you have linked appears to be caused by CONF-11555.

            We will take into account your suggestion for creating a JMX component, as it does sound like a good idea.

            Regards,
            Andrew Lynch

            Andrew Lynch (Inactive) added a comment - Igor, the registration of the c3p0 MBean is actually done within c3p0 itself and we have no control over this behavior. What you can do is specify the following system property: -Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator to prevent c3p0 from registering its MBean. The actual stack trace you have linked appears to be caused by CONF-11555 . We will take into account your suggestion for creating a JMX component, as it does sound like a good idea. Regards, Andrew Lynch

              shaffenden Steve Haffenden (Inactive)
              15d9a6950818 Igor Minar
              Affected customers:
              3 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: