c3p0-0.9.1.2: Built-In JMX-Service incompatible with Websphere 6.1.0.9

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 2.9.2
    • Affects Version/s: 2.9.1
    • Component/s: None
    • Environment:

      Problem:
      Confluence 2.8.0 didn't start up on Websphere 6.1 (extact version is 6.1.0.9).
      In the logs the following can be found (see also attached log snippet):

      creating bean with name 'sessionFactory' defined in class path resource [productionDatabaseContext.xml]: Invocation of init method failed; nested exception is java.lang.LinkageError: LinkageError while defining class: javax.managemen
      t.MBeanServer
      [...]
      java.lang.ClassFormatError
              [...]
              at com.mchange.v2.c3p0.management.ActiveManagementCoordinator.attemptManageC3P0Registry(ActiveManagementCoordinator.java:52)
      

      The problem could be tracked down to the JMX bean, that c3p0 tries to start internally in file ActiveManagementCoordinator.java, line 52.

      Workaround:
      Since this problem did'nt occur with Confluence 2.7.2 (the last version I installed), I simply replaced the c3p0-0.9.1.2.jar in Confluence-2.8 with the c3p0-0.9.0.4.jar from Confluence 2.7.2.
      This solved this problem and the confluence start up went on up to the very same problem as reported in CONF-11434 for Weblogic (same workaround for this works on Websphere 6.1.0.9).

            Assignee:
            Andrew Lynch (Inactive)
            Reporter:
            Stefan Prange
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: