Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4292

Deployment order based on jboss-all.xml doesn't work properly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              panos.mitronikas Panos Mitronikas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: