- The successful deployment of B.war requires A.war to be fully deployed first, but when server is restarted, the deployment order no longer exist, JBoss server seems to be stuck on "starting" status.
- Red Hat JBoss Enterprise Application Platform (EAP)
- Application B.war has dependency on application A.war during deployment time, two scenarios:
- EJB code
- REST service call
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.