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

Extending Log4j

Hi all, I have used log4j extensively, but I would like to extend its functionality, and I have some questions before I start. Below is what I would like to accomplish 1. Enhance Log4j logging by adding web specific information. 2. For Instance, log methods should not have the following method

Re: Extending Log4j

Using NDC or MDC may work for you. On Fri, 25 Mar 2005 09:00:13 -0500, Todd Nine <[EMAIL PROTECTED]> wrote: > Hi all, > I have used log4j extensively, but I would like to extend its > functionality, and I have some questions before I start. Below is > what I would like to accomplish > > 1. Enh

RE: Where to set exernal property referred to in log4j.properties

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

RE: Extending Log4j

If you're able to use log4j 1.3, you could use ReflectionFilter. Instead of passing a string in the debug call, pass in a JavaBean (POJO) and the ReflectionFilter will build an MDC entry for each JavaBeans-style attribute available on the object. The event's message is provided one of two way

RE: Where to set exernal property referred to in log4j.properties

At 09:33 AM 3/25/2005 -0500, you wrote: >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. Have you looked into using CATALINA_OPTS? Just set said variable as an

Log4J - Multiple instances, logging to STDERR

I have a Weblogic 8.1 application server, containing multiple EAR applications, made up of stateless session beans. The server is supposed to have one logger configured, with log4j.jar on the server's classpath and the config file residing on the disc rather than in the ear files. The problem we

RE: Where to set exernal property referred to in log4j.properties

Hi, > >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 th

RE: Where to set exernal property referred to in log4j.properties

Thanks for the insights on why to avoid writing to the same file from multiple JVMs, Andy - and for the properties suggestions Jake. -Original Message- From: Andy McBride [mailto:[EMAIL PROTECTED] Sent: Friday, March 25, 2005 11:00 AM To: 'Log4J Users List' Subject: RE: Where to set exe

Re: Where to set exernal property referred to in log4j.properties

Alternatively you could use a SocketAppender in one VM and SocketReceiver (log4j 1.3) or a SocketNode (1.2.x) in the other to receive logging events sent to the socket and log them as if they were generated in the same VM. These were added to log4j specifically for this purpose, if I recall corre