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

[Jess Holle (JIRA)]

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

Jess Holle commented on WFLY-3726:
----------------------------------

Actually the filesystem contents were very nearly appropriate as an ear.  Further analysis showed that the only issues was a single .rar file that was present but should not be actually deployed/activated.  We can rename/zip/remove/whatever this.  Doing so allows deployment via deployment scanner of the parent directory as an ear and the child directory as a war.

All that said, explicit deployment of the exploded war directory should also work -- and does up until a deployment scanner fails to deploy an application, at which point the <deployments> element is removed from standalone-full.xml, which is patently incorrect and the subject of this bug.

In short, for my use case I now have another workaround, but this bug is still quite valid.

> 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.2.6#6264)