[
https://issues.jboss.org/browse/WFCORE-4292?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-4292:
------------------------------------------
The WFCORE-4292 scenario sounds a lot like the WFCORE-4291 scenario (deployments in the
same server calling each other during boot) and I suspect 4292 is not a bug, it's the
same RFE as 4291.
Deployment order based on jboss-all.xml doesn't work properly
-------------------------------------------------------------
Key: WFCORE-4292
URL:
https://issues.jboss.org/browse/WFCORE-4292
Project: WildFly Core
Issue Type: Bug
Reporter: Panos Mitronikas
Priority: Major
Our application consists of a core module (ear or war) and several component modules
(wars) that register to the core upon deployment.
The process is implemented with a REST service available in the core module and REST
clients in each component that call a register method upon deployment and an unregister
upon removal. This requires a deployment order for server restarts and it is implemented
with jboss-all.xml files in each component war.
The process was smooth on Wildfly 10 but on 12 restarts seem not to follow the deployment
order, or for being exact it appears that the core REST service doesn't get
initialized properly and clients just hang there waiting, resulting in a total crash of
the server upon initialization (never goes up and crashes with some concurrency error
after 5 minutes).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)