EAP starts the deployment of the J2EE application before the messaging services are available

Issue

• When using colocated master-slave servers, if one node is stopped and then started again, the server tries to deploy the application before the JMS services are started.
• The application eventually gets deployed and all the MDBs are started as soon as the JMS services are up but the deployment throws the following error which does not indicate a healthy startup:

2019-09-16 15:10:28,393 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "application.ear")]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.ra.activemq-ra",
        "jboss.naming.context.java.ConnectionFactory",
        "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
    ],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => [