-
Bug
-
Resolution: Done
-
Major
-
2.1.3.SP1
-
None
-
None
-
Workaround Exists
-
When resolving virtual files,
1. DefaultVFSRegistry checks expiration of root context by IterableTimedVFSCache.findContext() which is implemented based on TimedCachePolicy.getValidKeys()
2. If the context is expired, a new context is created and CachePolicyVFSCache.putContext() is called, but the method checks the existence of cache entry by TimedCachePolicy.peek() which doesn't care about its expiration. Then the new entry won't be inserted into the cache and the expiration time of the old entry won't be updated.
So once cache entries are expired, caching won't work and contexts will be created again and again.
- is incorporated by
-
JBPAPP-3760 [JBVFS-134] IterableTimedVFSCache doesn't cache entries once they get expired
- Closed
- is related to
-
JBAS-7728 IterableTimedVFSCache leaks disk space when cache values get expired
- Closed
- relates to
-
JBVFS-137 When symbolic links are used for server configuration directories, the vfs cached deployments are not found within the CombinedVFSCache permanent roots
- Resolved