Hi
If it's not a must to write into the same log file: there are several
techniques to separate the logger universes in order that the same
package/class writes to different log files. The easiest way is by using the
fact that the different apps run in different thread contexts (I assume this
The log4j team is proud to announce the official release of log4j 1.2.12!
This new version contains a number of bug fixes, the addition of the much
requested TRACE level, and is compile and runtime compatible with the
earlier JDK's 1.1 and 1.2 (this feature had been inadvertently broken in
Thanks for the suggestion (I will investigate it as a possible solution), but
what if I have to write to the same log file?
-L
On Thu, Sep 08, 2005 at 09:58:34AM +0200, Bender Heri wrote:
Hi
If it's not a must to write into the same log file: there are several
techniques to separate the
Well, there is only so much you can fit into a dot release...:-) But we
will certainly take the patch into consideration for the 1.3 release too. I
don't know how likely it is at this point (we need to review the tasks,
etc), but we were hoping to have 1.3 released before the end of this year.
Sorry .. I forgot to type a subject in my earlier mail/..
I am new to log4j..
I have a web project in which I have log4j.properties under
WEB-INF/classes folder and I do configure log4j during application start
up using one of my servlet.
as shown below
Scott Deboy sdeboy at comotivsystems.com writes:
hostname and application properties MDC are concatenated to determine the
tab routing..you can change
this in the app-wide prefs window.
By the way, socket-based appenders define the hostname property for you -
that's why you see two tabs.
You need an 'application' property that is added to every event
processed by an appender (this application property would be unique per
appender). Once the application property is added to every event, you
can use the default tab identifier in Chainsaw and have events route
correctly to tabs (one
