[jbosstools-issues] [JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-18861:
-------------------------------------

This absolutely sucks... because it means my remote servers in RSE+mgmt mode will experience this bug, and will, in fact, require access to the filesystem locations. 

When using mgmt to stop a deployment, the server creates a .undeployed marker.  If, after a restart, we try to start it, it will fail. 

I would argue this is an upstream bug, but, since we can't expect fixes for the various as7-wf releases, we still need to deal with it.   

This is my angry face.  >=[

> module start action does not delete *.undeployed file
> -----------------------------------------------------
>
>                 Key: JBIDE-18861
>                 URL: https://issues.jboss.org/browse/JBIDE-18861
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>         Environment: Windows7 64bit, JDK 8u25
>            Reporter: Darryl Miles
>            Priority: Minor
>             Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>
> If you start Wildfly with all modules enabled and started.
> Now use STOP action on an EAR module.
> Now stop Wildfly.
> Now start Wildfly (debug or run).
> It will start up without the EAR module running, this is correct behavior at this point.
> Now use START on EAR module.  It fails to start at all.
> This is because the file *.undeployed still exists.  If you manually remove the file (using system file manager) the module will start up.
> If you perform a "full publish" on the module that appears to cause it to start up as well.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)