Hi,
I got the similar problem of you and I finally discover what is the problem.
First I use wsad 5.0 and use the express server that is built in wsad 5.0.
So your problem is not using log4j but log4j with commons-loggins.jar.
When you call private static Log log =
Hi,
Is anybody working on/maintaining Chainsaw? I'd like to use it with the
SocketHubAppender. I have downloaded some modifications to allow use of
the SocketHubAppender that I found in an old post but that doesn't seem
to be part of the latest release.
-Dave
Yep. In fact changes have just recently been made in the current cvs
version to support the new receiver framework. This will allow it to work
with SocketHubAppender, JMSAppender, or any appender that has a matching
receiver. Configuration of Chainsaw is now handled via the normal log4j xml
Hi,
As someone who has made quite a bit of use of print statements to track
execution through code, and then hates to go back and remove those print
statements, I just want to say thanks to those who have developed log4j
and added it to the Jakarta project so that others (me) can make use of
Agreed!!!
-Original Message-
From: Erik Price [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 5:01 PM
To: Log4J Users List
Subject: thanks
Hi,
As someone who has made quite a bit of use of print statements to track
execution through code, and then hates to go back and
At 01:51 PM 4/1/2003 -0800, you wrote:
It is still alpha, but you could try building the current cvs and giving it
a try.
Ceki, et al, I know there is no definitive deadline for v1.3, and I think it
is still early, but I wonder if we should consider doing an alpha build at
some point? Something
