[jboss-jira] [JBoss JIRA] (AS7-4175) Deployment content is not always removed from data/content

[Brian Stansberry (JIRA)]

Brian Stansberry created AS7-4175:
-------------------------------------

             Summary: Deployment content is not always removed from data/content
                 Key: AS7-4175
                 URL: https://issues.jboss.org/browse/AS7-4175
             Project: Application Server 7
          Issue Type: Bug
          Components: Domain Management
    Affects Versions: 7.1.1.Final, 7.1.0.Final
            Reporter: Brian Stansberry
            Assignee: Kabir Khan
            Priority: Critical
             Fix For: 7.1.2.Final
         Attachments: test-ds.xml

The AS7-341 fix doesn't seem to be working in some use cases.

I'll attach a test-ds.xml that can be used to manual reproduce this. Using a -ds.xml is useful since it's trivial to modify the deployment file to create a new hash.

>From the CLI, this works (i.e. when both steps are done there are zero additional subdirectories in data/content, i.e. zero total directories on a fresh install):

[standalone at localhost:9999 /] deploy /home/me/test-ds.xml
[standalone at localhost:9999 /] undeploy test-ds.xml

However, this does not work (i.e. when both steps are done there is one additional subdirectories in data/content, i.e. one total directory on a fresh install):

[standalone at localhost:9999 /] deploy /home/me/test-ds.xml

manually modify /home/me/test-ds.xml

[standalone at localhost:9999 /] deploy --force /home/me/test-ds.xml

There may be other permutations of the of deploy/redeploy/undeploy that also leave file behind. In particular, the forum thread references using the jboss maven plugin, so whatever ops it is invoking should be checked.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira