Bug 21818 - Tomcat forgets "allowLinking=true" setting when reloading web applications
Summary: Tomcat forgets "allowLinking=true" setting when reloading web applications
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Unknown (show other bugs)
Version: 4.1.31
Hardware: Macintosh All
: P3 normal with 2 votes (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
: 17557 22869 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-07-23 03:25 UTC by Ron Newman
Modified: 2005-02-28 13:02 UTC (History)
2 users (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Newman 2003-07-23 03:25:26 UTC 
If I have this in my server.xml

<Context path="/foo" 
      docBase="foo" 
        debug="0"
   reloadable="true" 
 crossContext="true">
 <Resources className="org.apache.naming.resources.FileDirContext"
         allowLinking="true"/> 
</Context> 

Tomcat forgets the allowLinking="true" setting if
   (a) I edit the application's web.xml file, triggering an automatic reload, or
   (b) I use Tomcat Manager to Stop the application and then Start it again

After I do either of these things, Tomcat can no longer find any resource in the application if it has 
to traverse a symbolic link.
Comment 1 Ville Sulko 2004-02-16 11:14:13 UTC 
This behaviour is still there in 4.1.29. Running on Linux/RH9 and Sun JDK 
1.4.2_03.

This is actually quite annoying, as it means that when one context using 
symlinks needs to updated, the whole tomcat must be restarted...
Comment 2 Stephoule 2004-11-17 16:55:07 UTC 
This behaviour is still there in 4.1.31. Running on HP-UX B.11.00 and Sun JDK 
1.4.2_05.  Is there a fix for that?
Comment 3 Yoav Shapira 2004-11-17 17:10:39 UTC 
Updating version to 4.1.31 to reflect your testing.  The suggestion is, and has 
been for over a year now, to upgrade to 5.x, because 4.x is not actively 
maintained.
Comment 4 Mark Thomas 2004-11-19 21:55:03 UTC 
This has now been fixed in CVS HEAD. As Yoav noted it has been fixed in 5.x 
for some time.

Please note that whilst I have every intention of releasing a 4.1.32 at some 
point, there are no firm plans present and I don't see it happening until the 
New Year at the earliest.
Comment 5 Mark Thomas 2004-12-22 22:49:25 UTC 
*** Bug 17557 has been marked as a duplicate of this bug. ***
Comment 6 Mark Thomas 2005-02-28 22:02:04 UTC 
*** Bug 22869 has been marked as a duplicate of this bug. ***