static loggers (was Logger serialization)

There are situations where you cant use static members. If you separate logging universes by using a specialzed RepositorySelector, which returns different loggers depending on diffenrent MDC values. If the basic framework classes, which are used in different applications (moduls), but running

Logging Event

Hi , In my application i need to get some more information in the LoggingEvent for e.g thread id along with thread name and some other information as well. Do I need to extend log4j for this and create new Event to be passed? Please help -George S

Maybe a small problem with my configuration?

Dear list Maybe it is supposed to be like that, but I will ask anyway: In my Application at startup if I use BasicConfigurator.configure() I get the following console output: [Session started at 2005-11-29 11:47:55 +0100.] *** configurationOptionStr=null ** End of LogManager static

RE: Logging Event

The specifier t within the layout pattern renders the thread name to the output. I dont know how to output the thread ID. what do you mean by some other information? You can put some values into the MDC before calling a logging function. Within the layout you can render this values again:

Re: log4j and weblogic help needed

Quoting kalohr [EMAIL PROTECTED]: It's a good idea! I did not know about classloading config options, I thought that each ear is by default loaded by a chlid classloader which uses the libs within the ear. Never verified if Weblogic really works in that manner. I 'll look into it and I will

Re: Maybe a small problem with my configuration?

I take it you are using Logj4-1.3alpha. Which one? I suggest using the latest alpha7. However, if you aren't specifically using anything that Log4j-1.2.xx doesn't already provide, I suggest going with that rather than 1.3alpha builds. Anyway, 1.3alpha uses itself to log. That means that if

RE: Logging Event

Or you could try something like the following to set the thread name MyThread myThread = new MyThread(); myThread.setName(MyPrefix- + myThread.getId()); myThread.start(); Regards Tim A -Original Message- From: Bender Heri [mailto:[EMAIL PROTECTED] Sent: Tuesday,

Log4j not parsing my XML. Please help

Hi all, I'm using log4j1.2.12. When i start my application the xml parsing fails.. It throws the following exception:: log4j:WARN Fatal parsing error 29 and column -1 log4j:WARN Expected /appender-ref to terminate element starting on line 28. log4j:ERROR Could not parse file

Re: Logger serialization

Curt Arnold wrote: On Nov 28, 2005, at 5:18 PM, Trenton D. Adams wrote: Trenton D. Adams wrote: Huh, serialization on a static variable? To my knowledge, that doesn't happen anyhow. LOL Ok, forget that one. What about on an instance variable? Logger is not serializable (and

Re: Logger serialization

[EMAIL PROTECTED] wrote: On Nov 28, 2005, at 6:28 PM, Trenton D. Adams wrote: I can't see using anything other than the root logger. Can you? Am I missing something? I have 3 reasons for using loggers other than the root logger: 1. Differential logging levels. In both development, and

Re: Log4j not parsing my XML. Please help

Hi Jake, Thanks for ur reply.. After placing the xml in the dir where my class file is present, everything works fine. But i don't understand why it fails to parse, if i place it in some other dir and loads it using Loader.getResource(String url) method. I guess if we didn't give level to the

Re: Logging Event

Hi, My is application is something like this I have some components as the part of it and all the components works in a single process but may be different threads. And I want all the components to log to a single file. So in the single file I shuld get a component name as well so that i can