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
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"
This is odd, we're using this feature with log4j 1.2.8 in
production. Maybe it's something in log4j1.2.13 that is different.
If you had the time, would you be able to try log4j1.2.8 temporarily
to confirm that works for you? (would help me isolate what I should
do to fix this).
cheers,
I've done as suggested. It has worked smoothly, by manually configuring
the Appender in the app and the Receiver in Chainsaw.
So, as it was just a test of the "coolness" of the ZeroConf Chainsaw
feature, I'm not desperate to make it work. I dont have to manage dozens
of apps/logs (although it wo
Exception in thread "Thread-0" java.lang.NoSuchMethodError:
org.apache.log4j.spi.ComponentBase.access$701(Lorg/apache/log4j/net/
SocketHubAppender;)Lorg/apache/log4j/ULogger;
at org.apache.log4j.net.SocketHubAppender$ServerMonitor.run
(SocketHubAppender.java:392)
at java.lang.Thread.ru
I've been using log4j in a desktop app for a while. I tried to use
Chainsaw v2 to watch the log while the app is being tested, from another
computer, using ZeroConfSocketHubAppender.
I made all the necessary steps to add required jar files and modified
log4j.xml config file to use the appender.
