Hi Lesley,
Looking at your log4j.xml file it appears that you are defining several
AsyncAppenders, actually 6 of them which does not explain why there are 12
AsyncAppender threads. At some point in time, you have probably restarted the
web-application (or reloaded log4j) without shutting down
rs.
Is that right?
Thanks,
Lesley
-Original Message-
From: Ceki Gulcu [mailto:c...@qos.ch]
Sent: Thursday, 11 June 2009 5:57 PM
To: Log4J Users List
Subject: Re: log4j v1.2.14 compatible with Java 1.6?
Hello Lesley,
Thank you for the test case.
Indeed, multiple FileAppender instances loc
Hello Lesley,
Thank you for the test case.
Indeed, multiple FileAppender instances located in the same JVM and writing to
the same file is a source of error. Just use a single FileAppender instance per
file target.
AsyncAppender uses references to appenders. It does not create them on its o
-Original Message-
From: Ceki Gulcu [mailto:c...@qos.ch]
Sent: Thursday, 11 June 2009 12:23 AM
To: Log4J Users List
Subject: Re: log4j v1.2.14 compatible with Java 1.6?
I bet that more than two application instances are writing to the same log
file. If you have such a requirement, try logback
I bet that more than two application instances are writing to the same
log file. If you have such a requirement, try logback which supports
multiple JVMs writing to the same log file.
Lesley Tay wrote:
Hi all,
Wondering if anyone has tried running log4j 1.2.14 using Java 1.6.0_11?
Have you c
ent: Wednesday, 10 June 2009 4:51 PM
To: Log4J Users List
Subject: Re: log4j v1.2.14 compatible with Java 1.6?
Lesley Tay skrev den 10-06-2009 04:45:
> By weird I mean null characters being printed out to the log at random times:
>
Do these random times coincid
Lesley Tay skrev den 10-06-2009 04:45:
By weird I mean null characters being printed out to the log at random times:
Do these random times coincide with the machines being booted?
--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
: log4j-user@logging.apache.org
> Subject: log4j v1.2.14 compatible with Java 1.6?
>
> Hi all,
>
> Wondering if anyone has tried running log4j 1.2.14 using Java 1.6.0_11?
> Have you come across any weird issues?
>
> By weird I mean null characters being printed out to the lo
Hi all,
Wondering if anyone has tried running log4j 1.2.14 using Java 1.6.0_11?
Have you come across any weird issues?
By weird I mean null characters being printed out to the log at random times:
2009-06-02 08:55:13,475 server1 principal logging-text
2009-06-02 08:55:14,872 server1 principal log
