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

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Wed Dec 19 09:52:08 EST 2012


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

Brian Stansberry updated AS7-6031:
----------------------------------

    Comment: was deleted

(was: This sounds familiar; I believe it may be a duplicate. I commented on the other issue with some thoughts.)

    
> 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
>
> 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


More information about the jboss-jira mailing list