This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Our application requires Tomcat 5.5, which is not provided by us, but installed by the customers themselves. On MS-Windows installations it happens often (~15% of all Windows installations) that there is no localhost<date>.log written, but the stdout<date>.log shows the following message after startup:
Our own webapplication logs fine to the logfile definied in its own log4j-configuration and
the stdout<date>.log, stderr<date>.log and jakarta<date>.log are written to %TOMCAT%\logs\
Why is the tomcat looking at these installations for a log.properties in the C:\WINDOWS\system32 tree? (I know it is the directory from where the service is started, but other tomcats started as Service do not show this behaviour).
And how should this log.porperties look like? Should it be a copy of %TOMCAT%\conf\logging.properties?
I'd like to thank in advance for any help!
Best regards, Florian Anwander
Joined: Jan 08, 2009
Florian Anwander wrote:Why is the tomcat looking at these installations for a log.properties in the C:\WINDOWS\system32 tree?