Again, wrong. allowLinking applies to any web-app resources. Only internal
Tomcat file access (bin, lib, logs etc) goes directly to the file system.
And for what it's worth, allowLinking appears to have fixed it :)
It manifested itself really silently and I didn't see anything about it in
Tomcat 6.0.16
Linux 2.6.18
JDK 1.6.0_05
Imagine a webapp like this:
/index.jsp
/WEB-INF
-web.xml (of course)
-/classes
--ConfigFile.txt
-/lib
--MyConfigLoader.class
... and imagine that .class file is inside a .jar file :) Sorry about that.
John
Ok ok i know this is very much not a one size fits all sort of question,
but I'm just wondering what those out there have. How many webapps do
you have per instance? What is recommended (one, three, 10, 40 i have
no idea) ? Hardware specs are probably about the norm these days, 2 G
of ram dual
Hi,
This is a nasty problem but I hope someone out there has figured it out.
We have been using tomcat 5.5.17, IIS 6, and JK2 happily for about a
year now. Up to this point, we have not used IIS directory security to
pass the NT username to tomcat. Some of our webapps have no security
