Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-339

Sometimes MSOCommonBPMN war failed to be deployed in JBOSS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • Amsterdam Release

      Sometimes it happens that MSOCommonBPMN war failed to be deployed in JBOSS.

      It fails with error saying:

      NoSuchMethodError: org.springframework.util.xml.SimpleSaxErrorHandler.<init>(Lorg/apache/commons/logging/Log

       

      The reason to that failure is conflict between dme2-3.1.200.jar (dependency in dmaapClient jar) and Spring jars.

      The dme2-3.1.200.jar contains Spring classes that were customized (Log was replace there with ATT Log).

       

      As temporary fix it's possible to that by simply exclude dme2-3.1.200.jar, but it might be that fix can cause some other issues in run time.

      <dependency>
      <groupId>com.att.nsa</groupId>
      <artifactId>dmaapClient</artifactId>
      <version>0.2.12</version>
      <exclusions>
      <exclusion>
      <groupId>com.att.aft</groupId>
      <artifactId>dme2</artifactId>
      </exclusion>
      </exclusions>
      </dependency>

      But it actually required to fix the code in dme2-3.1.200.jar and to release a new version of dmappClient jar.

       

      BTW - there is another dmmapClient jar published under other group Id(see below), but it also include dependency to the same dme2-3.1.200.jar.

      <groupId>org.onap.dmaap.messagerouter.dmaapclient</groupId>
      <artifactId>dmaapClient</artifactId>
      <version>1.0.0</version>

       

            eyalholz eyalholz
            eyalholz eyalholz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: