[jboss-jira] [JBoss JIRA] (WFLY-10344) Deployment order based on jboss-all.xml doesn't work properly

Panos Mitronikas (JIRA) issues at jboss.org
Tue May 8 03:22:00 EDT 2018


Panos Mitronikas created WFLY-10344:
---------------------------------------

             Summary: Deployment order based on jboss-all.xml doesn't work properly
                 Key: WFLY-10344
                 URL: https://issues.jboss.org/browse/WFLY-10344
             Project: WildFly
          Issue Type: Bug
    Affects Versions: 12.0.0.Final
            Reporter: Panos Mitronikas
            Assignee: Jason Greene


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.5.0#75005)


More information about the jboss-jira mailing list