[jboss-jira] [JBoss JIRA] (AS7-783) Deployment scanner service should use a separate operation for each deployment

[George Plymale (JIRA)]

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

George Plymale commented on AS7-783:
------------------------------------

This is a very frustrating "feature."  We have several apps on one server (Using TorqueBox) and unfortunately when one app fails deployment, it cascades to ALL apps.  Please allow us to change this functionality or advise as to how we can stop this cascading failure.  I suspect that the only option right now is touching .dodeploys at delayed intervals.

> Deployment scanner service should use a separate operation for each deployment
> ------------------------------------------------------------------------------
>
>                 Key: AS7-783
>                 URL: https://issues.jboss.org/browse/AS7-783
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>             Fix For: No Release
>
>
> The scanner is creating a single composite op for all deployments encountered in a scan, rather than individual ops. The effect is failures in on deployment results in rolling back the others.
> This makes some sense when users change things after startup, since multiple changes within one scan are probably related to each other. But it's not the correct behavior at startup, since multiple apps may not be interrelated.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)