com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.

Atlassian JIRA | Dave Loeng [Atlassian] | 7 years ago
  1. 0

    Since Confluence 3.1.x bundles it own version of the xerces parser (xercesImpl-2.9.1.jar specifically), attempting to start it up will result in this error: {noformat}ERROR [JBossContextConfig] XML error parsing: context.xml org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextConfig.java:552) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:538) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279) {noformat} Attempting to remove Confluence's version and fallback on the version bundled with JBoss will result in the following error during as the user attempts to progress through the Confluence Setup Wizard: {noformat}com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:127) {noformat} The above exception is thrown due newer versions of the atlassian-plugin module that is stricter about older versions of xerces in the classpath (see https://studio.atlassian.com/browse/PLUG-414). In order to support JBoss, we need a context that is isolated from their WAR classloader. See https://jira.jboss.org/jira/browse/JBAS-7210. JIRA 4.0 has the same issue and is also waiting for this fix.

    Atlassian JIRA | 7 years ago | Dave Loeng [Atlassian]
    com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.
  2. 0

    Since Confluence 3.1.x bundles it own version of the xerces parser (xercesImpl-2.9.1.jar specifically), attempting to start it up will result in this error: {noformat}ERROR [JBossContextConfig] XML error parsing: context.xml org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextConfig.java:552) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:538) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279) {noformat} Attempting to remove Confluence's version and fallback on the version bundled with JBoss will result in the following error during as the user attempts to progress through the Confluence Setup Wizard: {noformat}com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:127) {noformat} The above exception is thrown due newer versions of the atlassian-plugin module that is stricter about older versions of xerces in the classpath (see https://studio.atlassian.com/browse/PLUG-414). In order to support JBoss, we need a context that is isolated from their WAR classloader. See https://jira.jboss.org/jira/browse/JBAS-7210. JIRA 4.0 has the same issue and is also waiting for this fix.

    Atlassian JIRA | 7 years ago | Dave Loeng [Atlassian]
    com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.
  3. 0

    Beta2 WAR file is not getting deployed in JBoss 4.2.3 GA. I get the following error in the atlassian-confluence.log file: {code} INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 176563 ms 2009-11-24 09:13:42,359 ERROR [main] [plugin.event.impl.DefaultPluginEventManager] notify Plugin Event Listener 'com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager@432a9e' threw an error on event 'com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@b87a95': Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. 2009-11-24 09:13:42,375 ERROR [main] [atlassian.confluence.event.ConfluenceEventManager] publishEvent An exception was encountered while processing the event: com.atlassian.confluence.event.events.admin.ConfluenceReadyEvent[source=com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager@177f8ad] com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85) {code} Checked the version of xerces.jar file in endorsed folder and it is the same version (2.9.1). Confluence 3.0.x war file is working fine on the same version of JBoss. Complete atlassian-confluence.log file is attached.

    Atlassian JIRA | 7 years ago | Appan Ponnappan
    com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Beta2 WAR file is not getting deployed in JBoss 4.2.3 GA. I get the following error in the atlassian-confluence.log file: {code} INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 176563 ms 2009-11-24 09:13:42,359 ERROR [main] [plugin.event.impl.DefaultPluginEventManager] notify Plugin Event Listener 'com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager@432a9e' threw an error on event 'com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@b87a95': Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. 2009-11-24 09:13:42,375 ERROR [main] [atlassian.confluence.event.ConfluenceEventManager] publishEvent An exception was encountered while processing the event: com.atlassian.confluence.event.events.admin.ConfluenceReadyEvent[source=com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager@177f8ad] com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed. at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85) {code} Checked the version of xerces.jar file in endorsed folder and it is the same version (2.9.1). Confluence 3.0.x war file is working fine on the same version of JBoss. Complete atlassian-confluence.log file is attached.

    Atlassian JIRA | 7 years ago | Appan Ponnappan
    com.atlassian.plugin.event.NotificationException: com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.
  6. 0

    [CONF-21385] Plugin notifications fail after cache manager has been shut down, logging switches to NOPLoggerRepository - Atlassian JIRA

    atlassian.com | 7 months ago
    com.atlassian.plugin.event.NotificationException: java.lang.RuntimeException: The CacheManager has been shut down. It can no longer be used.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.plugin.event.NotificationException

      com.atlassian.plugin.osgi.container.OsgiContainerException: Detected an incompatible version of Apache Xerces on the classpath. If using Tomcat, you may have an old version of Xerces in $TOMCAT_HOME/common/lib/endorsed that will need to be removed.

      at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast()
    2. com.atlassian.plugin
      DefaultPluginManager.init
      1. com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:85)
      2. com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:127)
      2 frames