Thanks for the reply, James. I agree with you that it wouldn't be non-standard but since I don't maintain our tomcat implementation I was looking to see if there might be another way.
Maybe making the logs relative to catalina.home is the right idea. I suppose that my only concern though is that I'm using my primary log file by both my web application and another external java application code. I mentioned this a couple days ago and someone suggested that sharing one log file between two applications is a bad idea and that the logs would become garbled. Is that really so? I thought that it was OK to share a log between different JVMs since the log includes thread identifiers. I'm probably going to move the applications that are outside the web application to a model whereby they are executed from URLs anyway so in the future I suppose that risk will be mitigated. -----Original Message----- From: James Stauffer [mailto:[EMAIL PROTECTED] Sent: Friday, March 25, 2005 8:38 AM To: Log4J Users List; [EMAIL PROTECTED] Subject: Re: Where to set exernal property referred to in log4j.properties On Fri, 25 Mar 2005 00:37:46 -0500, William Noto <[EMAIL PROTECTED]> wrote: > My operations team is concerned about setting the property externally at the > user level when we start Tomcat because they do not want to run a > non-standard implementation. That is equivalent to setting an environement variable and wouldn't make it a "non-standard implementation." > I have tried a number of things that I thought > might work including setting the property through the web.xml's > context-param tag and setting it in the <context> at the server.xml level > but always without success. Can you just use a relative path or chose a path relative to ${catalina.home} ? -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
