[jboss-jira] [JBoss JIRA] Resolved: (JBVFS-137) When symbolic links are used for server configuration directories, the vfs cached deployments are not found within the CombinedVFSCache permanent roots

[Ales Justin (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBVFS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ales Justin resolved JBVFS-137.
-------------------------------

    Fix Version/s:  2.2.0.Alpha3
       Resolution: Done


> When symbolic links are used for server configuration directories, the vfs cached deployments are not found within the CombinedVFSCache permanent roots
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBVFS-137
>                 URL: https://jira.jboss.org/jira/browse/JBVFS-137
>             Project: JBoss VFS
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.3.SP1
>            Reporter: Mike Clark
>            Assignee: Ales Justin
>             Fix For:  2.2.0.Alpha3
>
>
> When a symbolic link (symlink) is used for a server configuration directory (for example, <jboss-home>/server/elsewhere -> /somewhere/default) there is a mismatch between paths used for the CombinedVFSCache's permanentroots and those used to find items in the cache.
> "CombinedVFSCache" which is configured in <jboss-home>/server/<server-dir>/conf/bootstrap/vfs.xml.  In this configuration, several "permanentroots" are configured based on properties.  While the properites themselves utilize a path with the symlink, the URLEditor that converts the string to a URL will convert the path, resolving the symlink.  (This is because the URLEditor utilzes the org.jboss.util.Strings class which makes a call to java.io.File#getCanonicalFile())
> However, lookups make into the cache will utilize a non-resolved path and thus do not match the permanent roots.  Due to another bug, JBVFS-134, this bug can lead to duplicate entries in the <jboss-home>/server/<server-dir>/tmp/vfs-nested.tmp directory and, ultimately,  to disk full errors.

-- 
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