I'm using Log4J underneath JCL, and doing considerably more logging than
one entry per screen, and the performance of the one app I'm thinking of
in particular is stellar. And the hardware isn't anything grand and the
load is pretty significant, so I would say Log4J, in and of itself,
isn't th
In the most recent update to our system, I installed log4j 1.2.11. After
the update someone at our hosting facility finally noticed that the
application was taking a very long time to paint some screens. The
application was frequently painfully slow to begin with, but someone
latched on to log4j
Actually, there are permission problems in my environment with
connecting to servers on arbitary ports. I'm quite happy with the
original SocketAppender and SocketReceiver configuration.
Thanks!
Rakesh
-Original Message-
From: Rakesh Patel
Sent: 03 November 2005 10:57
To: Log4J Users Li
The static approach only works if you use only one logger repository. If you
want to separate logging universes i.e. by using MDC you have to instantiate a
logger for each instance of a class. Logging statements out of static helper
routines even need fetch the correct logger "inline" not via a
Make it final, too :->
--On Thursday, November 03, 2005 12:33 AM +0100 Laurent <[EMAIL PROTECTED]>
wrote:
Make it static so you only need one per class:
public class MyClass {
static Logger logger = Logger.getLogger(MyClass.class);
---
I have set up a configuration file using Log4j so that errors are logged
to Windows Event Viewer using NTEventLogAppender.
In Windows Event Viewer the categories are currently being recorded as
10001,20001,30001 etc where 10001 represents debug, 20001 represents
info, 30001 represents warn and 400
Hi Scott,
The SocketHubAppender/SocketHubReciever looks a much better choice.
I had a go but get Connection refused errors. Here's my remote log4j
configuration:
I set up the Chainsaw receiver with the port and ip address of the
remote box.
What have I missed?
Cheers
Rake
