tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parsons Technical Services" <>
Subject Re: **CONFIDENTIAL** Configuring Log4j in webapps
Date Mon, 07 Feb 2005 16:17:40 GMT
Sounds like a rights issue on the server. Make sure that the user that 
tomcat is running with has the needed rights on the directory.

If it is running as a service, you can still have a rights problem.

If at some point in the path you do not have the proper rights, it can 
prevent the use of relative paths.

How are you starting Tomcat? Service or user?


----- Original Message ----- 
From: "Ethan Cabiac" <>
To: <>
Sent: Monday, February 07, 2005 9:23 AM
Subject: **CONFIDENTIAL** Configuring Log4j in webapps

> Hi everyone,
>     I don't know if this is a Log4j problem or a Tomcat related issue but 
> I
> am posting here first because I already subscribe to this mailing list ;).
> I have two (theoretically) identical Tomcat webservers (Tomcat 5.0), one 
> on
> my local WinXP machine for dev/testing and one on the company's Win 2003
> Server machine for production.  When I setup my log4j files in my webapps 
> I
> use:
>     log4j.appender.A1.File=../logs/mywebapplog.log
> On my test machine this will work perfectly and even create the log file 
> on
> Tomcat startup if it does not exist. On my production database it will not
> work if I use relative path, I actually have to specify
> C:/path_to_logs/mywebapplog.log and if the file is not there already then
> Tomcat complains on startup and no log gets written for the webapp.  Like 
> I
> said, the two Tomcats are supposed to be identical, but maybe there is a
> configuration discrepancy I missed, or maybe this is a Log4j thing? Any 
> help
> is appreciated.
> -Ethan Cabiac
> ------------------------------------------------------------------------------
> This message (including any attachments) contains confidential information
> intended for a specific individual and purpose, and is protected by law.
>     If you are the intended recipient, this message is CONFIDENTIAL as per 
> Contract.
>     This message should not be disseminated to 3rd parties without prior 
> written
>     approval or consent from a Director of TRAX. Violation of Contract 
> Terms constitute
>     a breach and be cause for termination.
>     If you are NOT the intended recipient, you should delete this message 
> and are hereby
>     notified that any disclosure, copying, or distribution of this 
> message, or
>     the taking of any action based on it, is strictly prohibited. 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message