]
Bartosz Spyrko moved JBEAP-17991 to WFLY-12778:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12778 (was: JBEAP-17991)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Affects Version/s: (was: 7.1.6.GA)
(was: 7.3.0.CD17)
(was: 7.2.3.GA)
QE Test Coverage: (was: +)
EAR deployed on colocated master/slave servers does not wait for the
embedded JMS services to startup properly
--------------------------------------------------------------------------------------------------------------
Key: WFLY-12778
URL:
https://issues.jboss.org/browse/WFLY-12778
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Bartosz Spyrko
Assignee: Bartosz Spyrko
Priority: Major
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:
{code:java}
/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"
],
{code}
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.