[jboss-jira] [JBoss JIRA] Commented: (JBAS-7628) CombinedVFSCache fills tmp/vfs-nested.tmp for deployments not listed in permanentRoots

[Ales Justin (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12506554#action_12506554 ] 

Ales Justin commented on JBAS-7628:
-----------------------------------

Where does jmx-console deploy the ear-file?
Or why you cannot add the path to permanentRoots?
By default we only do standard JBoss paths: deploy/, deployers/, ...



> CombinedVFSCache fills tmp/vfs-nested.tmp for deployments not listed in permanentRoots
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-7628
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7628
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: VFS
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Dietmar Scheidl
>            Assignee: Ales Justin
>            Priority: Critical
>
> CombinedVFSCache starts to fill the harddisk with copies of nested libraries from ear-deployment.
> This happens only if the location of the deployment is not listed in permanentRoots.
> We encounter this behavior by using the jmx-console to deploy the ear-file.
> Space is stable for about 30mins. After that any request to the web application (JSF/Richfaces/Seam/EJB3/...) leads to a new copy of all nested libraries into the vfs-nested.tmp folder.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira