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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-1547:
-----------------------------------------------

Nikoleta Ziakova <nziakova at redhat.com> made a comment on [bug 1004383|https://bugzilla.redhat.com/show_bug.cgi?id=1004383]

In EAP 6.2.0 ER3 jboss-vfs was upgraded to 3.2.2.Final instead of 3.2.0.Final. Is this version correct, please?

Upgrade was made correctly and if the version is OK then I can set this issue verified.

Both EAP zip and Maven repo zip contain jboss-vfs-3.2.2.Final-redhat-1.jar

pom.xml in EAP src zip:
  <version.org.jboss.jboss-vfs>3.2.2.Final-redhat-1</version.org.jboss.jboss-vfs>
  <dependency>
      <groupId>org.jboss</groupId>
      <artifactId>jboss-vfs</artifactId>
      <version>${version.org.jboss.jboss-vfs}</version>
  </dependency>

eap6-supported-artifacts-6.2.0.Beta1.pom in Maven repo zip:
  <dependency>
    <groupId>org.jboss</groupId>
    <artifactId>jboss-vfs</artifactId>
    <version>3.2.2.Final-redhat-1</version>
  </dependency>
                
> 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