[jboss-jira] [JBoss JIRA] (WFLY-10221) Hot deployment causes cascading redeployment of dependent artfacts when using jboss-all.xml configuration files

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559789#comment-13559789 ] 

Brian Stansberry commented on WFLY-10221:
-----------------------------------------

In general across WildFly if Y depends on X and you bounce X, then Y is going to bounce too. This applies to deployments with dependency links via jboss-all.xml as well.  Otherwise there is no way to know if Y will still work correctly and the server has no understanding of its internal state. Plus the mere fact of bouncing X means there is a period of time where a stated dependency of Y is not present.

The app.ear.deployed marker does not get updated because the deployment scanner updates the markers to reflect the results of its own activity, i.e. seeing changed content and telling the server to deploy it.  It would be a minor Enhancement request to get that changed. If you'd like I can convert this to an Enhancement and move it to the WFCORE project.  I can't promise when we'd get to it though.

> Hot deployment causes cascading redeployment of dependent artfacts when using jboss-all.xml configuration files
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10221
>                 URL: https://issues.jboss.org/browse/WFLY-10221
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 11.0.0.Final
>            Reporter: John Doe
>            Assignee: Jason Greene
>            Priority: Minor
>
> Let's assume I have 2 files _app.ear_ and _framework.ear_ deployed in WildFly 11.
> _framework.ear_ needs to be deployed before _app.ear_ which is expressed by the _jboss-all.xml_ file contained in the app.ear/META-INF folder:
> {code:java}
> <jboss umlns="urn:jboss:1.0">
> <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
>      <dependency name="framework.ear" />
> </jboss-deployment-dependencies>
> </jboss>
> {code}
> Now something changes in _framework.ear_ and a redeployment of _framework.ear_ becomes necessary.
> _app.ear_ does get redeployed, too, immediately after a hot deployment of _framework.ear_ has been carried out.
> *Observations:* After the redeployment of _framework.ear_ a new _framework.ear.deployed_ marker gets created, but same does not hold for _app.ear.deployed_.
> In fact no new _app.ear.deployed_ gets created at all (same timestamp for this file as before) despite a redeployment takes place.
> Nevertheless, in the console I see a redeployment for the dependent _app.ear_ occurs.
> Extending the example above, this is time consuming when you have a couple of additional dependencies cascading through.
> I don't understand why this happens because _app.ear_ did not change.
> My expectation is that only a redeployment of _framework.ear_ will take place. In my opinion there is no reason to redeploy _app.ear_, too.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)