[jboss-jira] [JBoss JIRA] (WFLY-3726) Filesystem deployment scanner deployment failure removes unrelated deployments

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-3726:
----------------------------------------

Yes, this is true, and is a problem if you have multiple scanners. Scanner's have a name, so we could store that name as an attribute in the model, with 'undefined' for the usual case of non-scanner deployments. 

However, the existing 'persistent' flag identifies deployments that are not under a scanner's control at all. The war in the description wouldn't have 'false' as the value for that.

I think we should solve the basic case of discriminating between scanner and non-scanner deployments before worrying about the much more edgy case of multiple scanners. This is complex stuff and we need to be very careful and analyze everything before adding a new attribute to track which scanner controls what. I don't think we should delay fixing the basic case for that.

> Filesystem deployment scanner deployment failure removes unrelated deployments
> ------------------------------------------------------------------------------
>
>                 Key: WFLY-3726
>                 URL: https://issues.jboss.org/browse/WFLY-3726
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.0.0.Final
>         Environment: WIndows and Linux platforms both exhibit the issue
>            Reporter: Jess Holle
>            Assignee: Emmanuel Hugonnet
>
> If one's standalone-full.xml configuration contains something like:
> <deployments>
>   <deployment name="MyWebApp.war" runtime-name="MyWebApp.war" enabled="true">
>     <fs-exploded path="../../SomeDir/MyWebApp.war" relative-to="jboss.home.dir"/>
>   </deployment>
> </deployments>
> whether manually inserted (while the server is not running) or installed via the CLI via
>   /deployment=ServiceCenter.war/:add(runtime-name=ServiceCenter.war,content=[{archive=false,path="../../Windchill/ServiceCenter.war",relative-to="jboss.home.dir"}])
> and a deployment scanner like:
>   <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> 
>     <deployment-scanner name="1" path="../../../Applications" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-exploded="true"/> 
>   </subsystem> 
> a failure by a deployment-scanner to deploy an application (exploded in my case, though I'm not sure this makes a difference) will cause the explicitly listed <deployments> to be removed from the configuration!
> This occurs irrespective of the value used for auto-deploy-exploded and to <deployment> elements that had already successfully been deployed and started.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)