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

Thu May 13 17:00:27 EDT 2010

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

Sergiy Barlabanov commented on JBAS-7628:
-----------------------------------------

The problem is in the VFS cache implementation. See https://jira.jboss.org/jira/browse/JBPAPP-3760. The fix has been already made there (https://jira.jboss.org/jira/browse/JBVFS-134), but somehow it is not yet decided, which JBoss version will it go to. There is a lot of discussion in forums on this problem with vfs-nested.tmp and 30 minutes timeout, but the real reason is not described. https://jira.jboss.org/jira/browse/JBVFS-134 fixes the problem. Please link all existing bugs on vfs-nested.tmp topic to JBVFS-134 (JBAS-7628, JBAS-6673, etc.) in order to let people easier come to the correct information. And the great discussion on http://community.jboss.org/thread/2148?start=0&tstart=0 is actually on the same thing (at least at the end).
The only simple workaround to come over this problem is to set defaultLifetime of IterableTimedVFSCache to something like 1 year in vfs.xml. The usage of other PathMatchingVFSCache implementations like just TimedVFSCache or LRU does not help, since the problem lies in the superclass of these both implementations (CachePolicyVFSCache). Subclasses of IterableVFSCache would be another possible alternative.

> 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