You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/09/02 03:36:08 UTC

DO NOT REPLY [Bug 22869] New: - under liveDeploy a webapp may throw an exception on restart. if some files are soft links

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22869>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22869

under liveDeploy a webapp may throw an exception on restart. if some files are soft links

           Summary: under liveDeploy a webapp may throw an exception on
                    restart. if some files are soft links
           Product: Tomcat 4
           Version: 4.1.27
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: ian@perth.wni.com


With the "allowLinking" set to true for example:

<Context path="" docBase="../blah">
<Resources className="org.apache.naming.resources.FileDirContext"  
allowLinking="true"/>
</Context>

Then if the web.xml is touch the subsequest restart of the webapp will
throw.
Reason: During the stop the FileDirContext.release() method is called.
resetting allowLinking to false (via StandardContext.resourcesStop() method)
Once restarted any links are not followed and the system startup will fail.

Solution: ? clearer semantics on what "stopping" means. Should 
release() be split into two methods release() and reset(). Currently
I've just commented-out the resetting of the allowLinking and caseSesitive
flags.