You might be able to extend FileAppender
On Wed, May 28, 2008 at 9:23 AM, Armin Häberling
<[EMAIL PROTECTED]> wrote:
> Curt Arnold wrote:
>>
>> On May 26, 2008, at 6:52 AM, Armin Häberling wrote:
>>
>>> Hi all,
>>>
>>> I'm facing the following problem. We have a tomcat instance with multiple
>>> w
See...
http://wiki.apache.org/logging-log4j/AppContainerLogging
And avoid Logger Repository Selectors which perform selection based on
Classloader. Use JNDI instead.
Jake
On Wed, 28 May 2008 17:59:33 +0300
Juha Laiho <[EMAIL PROTECTED]> wrote:
Armin Häberling wrote:
I'm facing the followi
Armin Häberling wrote:
I'm facing the following problem. We have a tomcat instance with
multiple webapps. The apps share many libraries in shared/lib directory,
some of them use log4j and some apache commons-logging.
Currently all the apps log to the same log file, which is suboptimal. We
lik
Curt Arnold wrote:
On May 26, 2008, at 6:52 AM, Armin Häberling wrote:
Hi all,
I'm facing the following problem. We have a tomcat instance with
multiple webapps. The apps share many libraries in shared/lib
directory, some of them use log4j and some apache commons-logging.
Currently all th
On May 26, 2008, at 6:52 AM, Armin Häberling wrote:
Hi all,
I'm facing the following problem. We have a tomcat instance with
multiple webapps. The apps share many libraries in shared/lib
directory, some of them use log4j and some apache commons-logging.
Currently all the apps log to the
Hi all,
I'm facing the following problem. We have a tomcat instance with
multiple webapps. The apps share many libraries in shared/lib directory,
some of them use log4j and some apache commons-logging.
Currently all the apps log to the same log file, which is suboptimal. We
like to have one
