Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-16381

Test compatibility with JBoss 5

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Installation
    • JBoss 5.0 GA
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We need to test JIRA compatibility with JBoss 5 which went GA recently.

      Currently following the JBoss 4.x installation instructions is to no avail. It seems JBoss ships a number of JARs in $JBOSS_HOME/lib/endorsed and/or $JBOSS_HOME/common/lib that are newer versions than those shipped with JIRA and cause problems trying to deploy JIRA.

      The following error is thrown whilst trying to deploy the dist-generic WAR:

      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)
      ...
      Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XML11Configuration
      	at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
      	at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
      	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown Source)
      

      Attempting to use the versions of files provided by JIRA results in JBoss being unable to start, and removing JAR files from the Jira WAR doesn't seem to resolve the situation.

              Unassigned Unassigned
              andrew.myers Andrew Myers [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: