[
https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi...
]
Bartosz Spyrko commented on WFLY-12778:
---------------------------------------
[~parsharma] I think so, it just needs to be a clustered messaging setup if I remember
right.
The problem is AMQ server starts in async way, if the data recovery/replication takes too
long, the deployment will fail because jms services depending on active AMQ are not
available.
EAR deployed on colocated master/slave servers does not wait for the
embedded JMS services to startup properly
--------------------------------------------------------------------------------------------------------------
Key: WFLY-12778
URL:
https://issues.redhat.com/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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)