Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20604

Statistics are read before deployment is deployed.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 7.4.0.CD21
    • MP Health, OpenShift
    • None
    • False
    • False
    • Undefined

      Check example-app-1-7kfbd.log to see this in logs.

      This is intermittent it happens with frequency (1:4). We encounter it more frequent on OCP3, but I hit it on OCP4 as well.

      This leads to health probe `boot-errors` DOWN and EAP pod can't get ready.

      sh-4.4$ curl localhost:9990/health{
         "status":"DOWN",
         "checks":[
            {
               "name":"boot-errors",
               "status":"DOWN",
               "data":{
                  "boot-errors":"[{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"subsystem\" : \"messaging-activemq\" },{ \"server\" : \"default\" },{ \"jms-queue\" : \"DLQ\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"subsystem\\\" => \\\"messaging-activemq\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"deployment\" : \"ROOT.war\" },{ \"subsystem\" : \"undertow\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"deployment\\\" => \\\"ROOT.war\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"subsystem\" : \"transactions\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"subsystem\\\" => \\\"transactions\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"deployment\" : \"ROOT.war\" },{ \"subsystem\" : \"undertow\" },{ \"servlet\" : \"com.redhat.xpaas.eap.deployments.servlet.EnableServlet\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"deployment\\\" => \\\"ROOT.war\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"subsystem\" : \"messaging-activemq\" },{ \"server\" : \"default\" },{ \"jms-queue\" : \"ExpiryQueue\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"subsystem\\\" => \\\"messaging-activemq\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"deployment\" : \"ROOT.war\" },{ \"subsystem\" : \"undertow\" },{ \"servlet\" : \"com.redhat.xpaas.eap.deployments.servlet.ServletCounter\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"deployment\\\" => \\\"ROOT.war\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"subsystem\" : \"undertow\" },{ \"server\" : \"default-server\" },{ \"http-listener\" : \"default\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"subsystem\\\" => \\\"undertow\\\")]' not found\"},{\"failed-operation\" : {\"operation\" : \"read-attribute\", \"address\" : [{ \"deployment\" : \"ROOT.war\" },{ \"subsystem\" : \"undertow\" },{ \"servlet\" : \"com.redhat.xpaas.eap.deployments.servlet.DisableServlet\" }]}, \"failure-description\" : \"WFLYCTL0216: Management resource '[(\\\"deployment\\\" => \\\"ROOT.war\\\")]' not found\"}]"
               }
            },
            {
               "name":"empty-readiness-checks",
               "status":"UP"
            },
            {
               "name":"server-state",
               "status":"UP",
               "data":{
                  "value":"running"
               }
            },
            {
               "name":"deployments-status",
               "status":"UP",
               "data":{
                  "ROOT.war":"OK"
               }
            },
            {
               "name":"empty-liveness-checks",
               "status":"UP"
            }
         ]
      }sh-4.4$
      

            jaslee@redhat.com Jason Lee
            mchoma@redhat.com Martin Choma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: