Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-4705

Bamboo 2.4 not compatible with jboss 4.2.x offending jar xercesImplxxx.jar

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 2.4 M1, 2.4
    • Installation
    • None

      since bamboo 2.4 the jboss endorsed library is rejected by bamboo.
      jboss cannot be booted when removing the endorsed xercesImpl.jar in jboss

        1. jboss-error.log
          30 kB

          Form Name

            [BAM-4705] Bamboo 2.4 not compatible with jboss 4.2.x offending jar xercesImplxxx.jar

            Stephen Hall added a comment -

            Will this be fixed in the next version of Bamboo? It is preventing me from upgrading to either version 2.4 or 2.5.

            Stephen Hall added a comment - Will this be fixed in the next version of Bamboo? It is preventing me from upgrading to either version 2.4 or 2.5.

            Andrew added a comment -

            FAQ and 2.4 Upgrade Guide have been updated.

            Andrew added a comment - FAQ and 2.4 Upgrade Guide have been updated.

            sladey added a comment -

            We may need to update this faq or create a new faq.

            sladey added a comment - We may need to update this faq or create a new faq.

            Krystian Brazulewicz added a comment - - edited

            Works on:

            • 4.2.0
            • 4.2.1
            • 4.2.2

            Fails on:

            • 4.2.3

            This problem is definitely related to:

            I've applied application classloader isolation in the atlassian-bamboo-2.4.0.war

            WEB-INF/jboss-web.xml
            <jboss-web>
    <class-loading java2ClassLoadingCompliance="false">
        <loader-repository>
            com.example:archive=atlassian-bamboo-2.4.0.war
            <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
        </loader-repository>
    </class-loading>
</jboss-web>

            and I've got typical for this problem ClassCastException

            java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory
    at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128)

            My suggestion is to downgrade jboss to version 4.2.2

            Krystian Brazulewicz added a comment - - edited Works on: 4.2.0 4.2.1 4.2.2 Fails on: 4.2.3 This problem is definitely related to: http://www.jboss.org/community/wiki/WhydoigetjavalangClassCastExceptionorgapachexercesparsersXIncludeAwareParserConfigurationinAS-5 https://jira.jboss.org/jira/browse/JBAS-7210 http://jira.atlassian.com/browse/JRA-16381 I've applied application classloader isolation in the atlassian-bamboo-2.4.0.war WEB-INF/jboss-web.xml <jboss-web> <class-loading java2ClassLoadingCompliance= "false" > <loader-repository> com.example:archive=atlassian-bamboo-2.4.0.war <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </class-loading> </jboss-web> and I've got typical for this problem ClassCastException java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128) My suggestion is to downgrade jboss to version 4.2.2

            Ulrich Kuhnhardt [Atlassian] added a comment -

            jboss 510 does not deploy bamboo either

            Ulrich Kuhnhardt [Atlassian] added a comment - jboss 510 does not deploy bamboo either

              Unassigned Unassigned
              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              Affected customers:
              2 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: