Hi Scott,
since my day is already saved I got it working with 1.3alpha-6 (even at
9pm in Old Europe).
Another quick question since I'm not too familiar with the new version -
I get the following exception
Testcase: [EMAIL PROTECTED]: Caused an ERROR
(class: org/apache/avalon/framework/logger/Log4JLogger, method:
isFatalErrorEnabled signature: ()Z) Incompatible argument to function
java.lang.VerifyError: (class:
org/apache/avalon/framework/logger/Log4JLogger, method:
isFatalErrorEnabled signature: ()Z) Incompatible argument to function
at
at.it20one.eprocurement.service.signature.SignatureServiceTestSetup.initialize(SignatureServiceTestSetup.java:87)
at
at.it20one.eprocurement.service.signature.SignatureServiceTestSetup.access$000(SignatureServiceTestSetup.java:22)
at
at.it20one.eprocurement.service.signature.SignatureServiceTestSetup$1.setUp(SignatureServiceTestSetup.java:55)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.extensions.TestSetup.run(TestSetup.java:23)
The avalon-framework-impl-4.2.0-jar and the new
avalon-framework-impl-4.3-jar uses Log4JLogger.isFatalErrorEnabled ()
... I assume that the method was long depracted and gone for ages ... :-)
Cheers,
Siegfried Goeschl
Scott Deboy wrote:
Yes, you can process events containing MDC and location info if the SocketAppender being used is from the latest log4j 1.3alpha jar.
Scott
-----Original Message-----
From: Siegfried Goeschl [mailto:[EMAIL PROTECTED]
Sent: Tue 9/6/2005 11:15 AM
To: Log4J Users List
Subject: Re: Problems to use Chainsaw V2 using SocketAppenders
Hi Scott,
that did the trick ... :-)
One quick question - if I would use 1.3alpha6 than the location info
does work?
Thanks in advance
Siegfried Goeschl
Scott Deboy wrote:
set locationInfo=false
Log4j 1.2.x socketappender -> Chainsaw V2 SocketReceiver can't read events that
contain location info or MDC until we make the LoggingEvent fully
serial-compatible between log4j 1.2.x and log4j 1.3
Also, if you use SocketAppender with other appenders (particularly
fileAppender), make sure the socketappender is referenced first in the list of
appenders - because %L, %M, patterns in a fileAppender layout will create
location info automatically - the logging event is then handed off to the
SocketAppender, but it already contains location info, and can't be serialized.
If you need location info in Chainsaw V2, use a FileAppender with the %F, %L,
%M patterns in the layout, and configure Chainsaw V2 with a
LogFilePatternReceiver.
Scott
-----Original Message-----
From: Siegfried Goeschl [mailto:[EMAIL PROTECTED]
Sent: Tue 9/6/2005 10:43 AM
To: [email protected]
Subject: Problems to use Chainsaw V2 using SocketAppenders
Hi folks,
I came across the Chainsaw V2 and thought it would save my day but I'm
unable to get it running ....
+) I updated to log4j 1.2.11 since 1.3alpha6 breaks my code
+) I can use the old chainsaw with no problem
+) I never get any logging event using Chainsaw 2.0alpha
Any ideas what went wrong ....
Thanks in advance
Siegfried Goeschl
CHAINSAW CONFIG
=============================================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration >
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";
debug="true">
<plugin name="SocketReceiver"
class="org.apache.log4j.net.SocketReceiver">
<param name="Port" value="4445"/>
</plugin>
<root>
<level value="debug"/>
</root>
</log4j:configuration>
LOG4J PROPERTIES
=============================================
og4j.appender.chainsaw=org.apache.log4j.net.SocketAppender
log4j.appender.chainsaw.remoteHost=localhost
log4j.appender.chainsaw.port=4445
log4j.appender.chainsaw.locationInfo=true
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
