Hello,
I have a requirement to log client sessions to different files, one file per
client. Whats the 'official' log4j way to do this? I have encountered the
term 'multiple hierarchy tree' several times, yet haven't been able to found
any usable information/code example of it.
regards,
rudi
Hello,
I'm writing some code that will turn log4j(1.2.8) logging on and off at
runtime. I'll probably expose this via jmx.
I've seen solutions out there to re-read a configuration file and this
is not what I want to do.
Instead, I want the code to discover all the loggers in use by my EAR
The difference can probably be explained as a difference in
LoggerRepositories. There is a servlet (LogWeb?) that allows config
changes so it migh have some clues to help you.
On 1/19/07, Ostermueller, Erik <[EMAIL PROTECTED]> wrote:
Hello,
I'm writing some code that will turn log4j(1.2.8) l
Does Jonas use something similar to the JBoss Unified Classloader? I don't
fully understand the Unified Classloader, but from what I've gathered, it seems
as if libraries, no matter where they are loaded from, are all part of one
uber-classloader. If this is true, and Jonas uses something like t
On Jan 19, 2007, at 4:19 AM, Rudi wrote:
Hello,
I have a requirement to log client sessions to different files, one
file per
client. Whats the 'official' log4j way to do this? I have
encountered the
term 'multiple hierarchy tree' several times, yet haven't been able
to found
any usable
Jake, thanks for your lengthy reply.
>> One way to solve the multiple classloader issue is to make sure
>> child-first classloading is disabled for any individual app
The pdf I referenced suggested the PARENT_LAST setting -- PARENT_FIRST
is the default.
Looking back at my settings, for some rea
The PARENT_LAST setting did the trick, thanks!
--Erik
-Original Message-
From: Ostermueller, Erik
Sent: Friday, January 19, 2007 2:37 PM
To: 'Log4J Users List'
Subject: RE: Missing loggers from getCurrentLoggers() under WAS 5.x
Jake, thanks for your lengthy reply.
>> One way to solve
At 05:03 PM 1/19/2007, you wrote:
>
>The PARENT_LAST setting did the trick, thanks!
>
I'm glad it worked, but I have to admit something. Child-First is
just another way of saying Parent-Last and it's what I recommend you
*not* use to avoid multiple separate instances of Log4j. Now I'm a
bit
