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/07/16 17:48:42 UTC
DO NOT REPLY [Bug 21659] New: -
LogSetter not created when adding a new context
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=21659>.
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=21659
LogSetter not created when adding a new context
Summary: LogSetter not created when adding a new context
Product: Tomcat 3
Version: 3.3.1 Final
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Major
Priority: Other
Component: Webapps
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: zorro.desbois@wanadoo.fr
Hi,
When I add a new context with the admin webapp, I don't have my
servlet logs.
I have a file apps-myAppli.xml with this content :
<?xml version="1.0" encoding="ISO-8859-1"?>
<Server>
<Host name="myAppli" >
<Context path="" docBase="/usr/webapps/myAppli" >
<LogSetter name="myAppli_log"
path="logs/myAppli_servlet-${yyyyMMdd-HH:mm}.log"
verbosityLevel="DEBUG"
servletLogger="true"/>
</Context>
</Host>
</Server>
For example, when I start tomcat, my context doesn't exist.
But, 2 minutes later, I add my new context with the webapps/myAppli.war and with
the file apps-myAppli.xml :
- the logFile myAppli_servlet-20030709-10:25.log is not created so there's no
servlet logs.
It seems that the ContextManager, when it adds a context, doesn't add its
interceptors like ContextXmlReader and LogSetter.
When I restart tomcat, the problem is solved.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org