Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12778

EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JMS
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1. Create 2 colocated servers. Server 1 will have master1 and slave2 while Server2 will have master2 and slave1

      2. Start both servers with standalone-full-ha.xml.

      3. Stop Server 1.

      4. Put an EAR with an MDB in the deployment directory of Server 1

      5. Start Server1

      At this point you'll see these errors in Server1 logs:

      14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: {
          "WFLYCTL0412: Required services that are not installed:" => [
              "jboss.ra.activemq-ra",
              "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
          ],
          "WFLYCTL0180: Services with missing/unavailable dependencies" => [
              "jboss.naming.context.java.comp.EJB_MDBEAR.EJB_MDB.TestMDB.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
              "jboss.deployment.subunit.\"EJB_MDBEAR.ear\".\"EJB_MDB.jar\".component.TestMDB.CREATE is missing [jboss.ra.activemq-ra]",
              "jboss.naming.context.java.module.EJB_MDBEAR.EJB_MDB.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"
          ]
      }
      
      
      Show
      1. Create 2 colocated servers. Server 1 will have master1 and slave2 while Server2 will have master2 and slave1 2. Start both servers with standalone-full-ha.xml. 3. Stop Server 1. 4. Put an EAR with an MDB in the deployment directory of Server 1 5. Start Server1 At this point you'll see these errors in Server1 logs: 14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread ) WFLYCTL0013: Operation ( "deploy" ) failed - address: ([( "deployment" => "EJB_MDBEAR.ear" )]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => [ "jboss.ra.activemq-ra" , "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" ], "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.naming.context.java.comp.EJB_MDBEAR.EJB_MDB.TestMDB.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]" , "jboss.deployment.subunit.\" EJB_MDBEAR.ear\ ".\" EJB_MDB.jar\ ".component.TestMDB.CREATE is missing [jboss.ra.activemq-ra]" , "jboss.naming.context.java.module.EJB_MDBEAR.EJB_MDB.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]" ] }

      Description

      When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs:

      /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: {
          "WFLYCTL0412: Required services that are not installed:" => [
              "jboss.ra.activemq-ra",
              "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
          ],
      
      

      When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs.
      Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either.

      The application should wait for its dependencies to be available.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  spyrkob Bartosz Spyrko-Smietanko
                  Reporter:
                  spyrkob Bartosz Spyrko-Smietanko
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated: