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/11/26 13:16:46 UTC
DO NOT REPLY [Bug 25013] New: -
Symbolic link related troubles should be locked as such.
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=25013>.
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=25013
Symbolic link related troubles should be locked as such.
Summary: Symbolic link related troubles should be locked as such.
Product: Tomcat 5
Version: 5.0.14
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Native:Integration
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: andreas.krueger@dv-ratio.com
On my machine, root (me) installed CATALINA_HOME.
To get Tomcat running, user (also me) constructed a farm of symbolic links
and called it CATALINA_BASE. Only files that I decide to change are real,
all else symbolic links.
As I have learned since, symbolic links are not supported out of the box.
This enhancement request is about making it easier for people like myself
to know what it is that is biting them.
The error messages I get are, e.g.,
SEVERE: Error reading tld listeners javax.servlet.ServletException:
Exception processing TLD at resource path
/WEB-INF/jsp2/jsp2-example-taglib.tld in context /jsp-examples
javax.servlet.ServletException: Exception processing TLD at resource path
/WEB-INF/jsp2/jsp2-example-taglib.tld in context /jsp-examples
at org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:696)
at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:348)
at org.apache.catalina.core.StandardContext.
start(StandardContext.java:4108)
at org.apache.catalina.core.ContainerBase.
addChildInternal(ContainerBase.java:866)
and so on (slightly edited for line breaks).
That give the unsuspecting user little clue.
No mention that "symbolic links" is the underlying problem.
I propose that Tomcat's logging, as it comes out of the box,
should be configured in such a fashion that
I'm told what I'm up against when things fail because of symbolic links.
I understand there is a specific test for symbolic links that fails,
so I would appreciate seeing the specific words "symbolic link" in
some log file.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org