[jboss-jira] [JBoss JIRA] (WFLY-1547) deploy directories not cleaned up

[Shaun Appleton (JIRA)]

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

Shaun Appleton commented on WFLY-1547:
--------------------------------------

I have tested  build #684 wildfly-8.0.0.Beta1-SNAPSHOT from https://ci.jboss.org/hudson/job/WildFly-latest-master/ dated 16Sep2013 


It looks good to me.

further details:

start wildfly in standalone mode with an ear deployed and using -Xrs 
then examine the vfs directory

[sappleto at localhost vfs]$ ls
deployment  temp
[sappleto at localhost vfs]$ tree
.
├── deployment
│   └── deployment66eab101a317e9dc
│       ├── jboss-as-ejb-in-ear-ejb.jar-11d777cd5d07eb11
│       │   ├── contents
│       │   └── jboss-as-ejb-in-ear-ejb.jar
│       └── jboss-as-ejb-in-ear-web.war-f6a6eb1501fcd144
│           ├── greeter.xhtml
│           ├── index.html
│           ├── META-INF
│           │   ├── MANIFEST.MF
│           │   └── maven
│           │       └── org.jboss.as.quickstarts
│           │           └── jboss-as-ejb-in-ear-web
│           │               ├── pom.properties
│           │               └── pom.xml
│           └── WEB-INF
│               ├── beans.xml
│               ├── classes
│               │   └── org
│               │       └── jboss
│               │           └── as
│               │               └── quickstarts
│               │                   └── ear
│               │                       └── controller
│               │                           └── Greeter.class
│               └── faces-config.xml
└── temp
    └── temp8214eb8231b421f
        └── jboss-as-ejb-in-ear-ear.ear-23e4035bb08c8d13
            ├── contents
            └── jboss-as-ejb-in-ear-ear.ear

21 directories, 10 files

kill wildfly and re-start 

examine vfs dir:


[sappleto at localhost vfs]$ tree
.
├── deployment
│   └── deployment2d33c8864573c359
│       ├── jboss-as-ejb-in-ear-ejb.jar-c4db878fe860c9a0
│       │   ├── contents
│       │   └── jboss-as-ejb-in-ear-ejb.jar
│       └── jboss-as-ejb-in-ear-web.war-af7a1f0b197d28ca
│           ├── greeter.xhtml
│           ├── index.html
│           ├── META-INF
│           │   ├── MANIFEST.MF
│           │   └── maven
│           │       └── org.jboss.as.quickstarts
│           │           └── jboss-as-ejb-in-ear-web
│           │               ├── pom.properties
│           │               └── pom.xml
│           └── WEB-INF
│               ├── beans.xml
│               ├── classes
│               │   └── org
│               │       └── jboss
│               │           └── as
│               │               └── quickstarts
│               │                   └── ear
│               │                       └── controller
│               │                           └── Greeter.class
│               └── faces-config.xml
└── temp
    └── temp8ea3b22d2b35a6c2
        └── jboss-as-ejb-in-ear-ear.ear-e47cb5a9268c7360
            ├── contents
            └── jboss-as-ejb-in-ear-ear.ear

21 directories, 10 files
[sappleto at localhost vfs]$

So no dir or file growth.



Repeating start, kill, start, kill, ... ,start, kill shows no growth in number of files or dirs
                
> deploy directories not cleaned up
> ---------------------------------
>
>                 Key: WFLY-1547
>                 URL: https://issues.jboss.org/browse/WFLY-1547
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Shaun Appleton
>            Assignee: jaikiran pai
>             Fix For: 8.0.0.Beta1
>
>         Attachments: deployment_with_hack_no_hook.txt
>
>
> 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