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

SO Fails Health Check with 503 error (logging?)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Amsterdam Release
    • Amsterdam Release
    • We don't see this issue at Integration lab and I would like to downgrade this one to medium. And don't suggest any fix at this moment.

      Hello as mkhinda said in -SO-208 (https://jira.onap.org/browse/SO-208?focusedCommentId=14894&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14894)-, we sometimes have this error when starting SO

       

      In so logs we can see: SO-503-2.txt

       

      07:17:01,075 ERROR [org.springframework.web.context.ContextLoader] (ServerService Thread Pool – 79) Context initialization failed: java.lang.NoSuchMethodError: org.springframework.util.xml.SimpleSaxErrorHandler.<init>(Lorg/apache/commons/logging/Log;)V
          at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.<init>(XmlBeanDefinitionReader.java:121)

       

      07:17:06,976 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "MSOCommonBPMN-1.1.0.war")]) - failure description: {
          "WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./mso/common" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./mso/common: java.lang.NoSuchMethodError: org.springframework.util.xml.SimpleSaxErrorHandler.<init>(Lorg/apache/commons/logging/Log;)V

       

            sdesbure sdesbure
            sdesbure sdesbure
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: