James, sorry for the slow reply. Thanks for posting this, it is
*exactly* what I needed. :)
Chris
On 6/20/06, James Stauffer <[EMAIL PROTECTED]> wrote:
Since it is really only useful for 1.2 (I thought 1.3 had something
that would do that) I didn't think there was much point to
contributing it.
And the troubles start:
Chainsaw detects the "new" ZeroConf appender, and given the fact
it's from the same station and name, Chainsaw "autoconnects" to it.
But... in the Receivers tree, my app appears twice, AND the log
entries appear twice, too.
If I repeat the process from step 3, a new re
I've had a similar problem... It seems like maxBackupIndex doesn't like
any #'s greater then 5 in some circumstances.
Try increasing your log size and decreasing the # of indexes.
See http://marc.theaimsgroup.com/?l=log4j-user&m=106321621416549&w=2 for
more information.
Jeremy
-Original
Test done.
It worked perfectly with log4j 1.2.8. I hope this helps isolating the
problem.
Now that I finally can use the ZeroConf feature, I have found a few
annoyances about how Chainsaw seems to handle it:
1 - I start my app.
2 - Chainsaw detects a ZeroConf appender. I check "autoconnect"
Hi all,
Here is my log4j.properties file :
log4j.rootLogger=OFF,
log4j.logger.com.actessud=DEBUG, stdout, R
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to output the caller's file name and line number.
log4j.app
