[jboss-jira] [JBoss JIRA] (AS7-6031) deploy directories not cleaned up

[Bartosz Baranowski (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Baranowski updated AS7-6031:
------------------------------------

    Git Pull Request: https://github.com/jbossas/jboss-as/pull/3816, https://github.com/jbossas/jboss-as/pull/3817  (was: https://github.com/jbossas/jboss-as/pull/3816)

    
> deploy directories not cleaned up
> ---------------------------------
>
>                 Key: AS7-6031
>                 URL: https://issues.jboss.org/browse/AS7-6031
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Shaun Appleton
>            Assignee: Bartosz Baranowski
>             Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories.
> The following reproduces this -
> i) ensure run.conf has the -Xrs set
> ii) ensure deployments has a deployable .ear in it
> iii) ./run standalone.sh and allow the deployments to deploy
> iv) stop the EAP process ie kill <process_id>
> v) observe content tmp/vfs
> (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP)
> This will eventually cause problems with lack of disk space.
> Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems.
> It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira