You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2005/01/14 19:29:45 UTC

DO NOT REPLY [Bug 31178] - Exception using Chainsaw for simple debugging

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31178>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31178





------- Additional Comments From kuki.szabolcs@gmail.com  2005-01-14 19:29 -------
I just want to let you know that this problem is still active, I've taken the
latest chainsaw code (using install-chainsaw.xml) + WebStart, tested with jdk
1.4.2. 

For SocketAppender I tested with log4j 1.2.8, 1.2.9, 1.3alpha.
I had beside the SocketApender an XMLLayot with locationInfo set

log4j.appender.fileXMLTARGET.layout=org.apache.log4j.xml.XMLLayout
log4j.appender.fileXMLTARGET.layout.LocationInfo=true

log4j.appender.CHAINSAW_CLIENT=org.apache.log4j.net.SocketAppender
log4j.appender.CHAINSAW_CLIENT.RemoteHost=127.0.0.1
log4j.appender.CHAINSAW_CLIENT.Port=4445
log4j.appender.CHAINSAW_CLIENT.LocationInfo=false

Changing the order (placing fileXMLTARGET after CHAINSAW_CLIENT) solved the
problem, any location information before the Appender will generate this exception.

As an ideea check where org.apache.log4j.spi.LocationInfo is refered and try to
fix it, so it would refer to org.apache.log4j.spi.location.LocationInfo.

Thanks for the great job :).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org