Re: Chainsaw Tab identifier

2008-03-06 Thread Jason Tholstrup
is no big deal. Once I've got this all flushed out and working would you like me to send you the upgraded version of SocketHubAppender? Any guide lines I'd need to follow to contribute it back? Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 6, 2008, at 11:12 AM, Scott Deboy wrote

Re: Chainsaw Tab identifier

2008-03-05 Thread Jason Tholstrup
; } /** * Returns value of the bApplication/b option. */ public String getApplication() { return application; } Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 3, 2008, at 4:49 PM, Scott Deboy wrote: log4j 1.3

Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
Long * THREAD threadString * PROP.keyName entry in the Property hashtable String * mapped to the key [keyName] Any help would be appreciated. Jason Tholstrup

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
javadocs that's enough. I'd just like to be able to tinker on my own. Thanks for all your hard work. Chainsaw is pretty cool. Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 3, 2008, at 11:42 AM, Scott Deboy wrote: Two things: 1. To get every socketappender connection to display

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
level value=debug/ /root /log4j:configuration Jason Tholstrup On Mar 3, 2008, at 11:42 AM, Scott Deboy wrote: Two things: 1. To get every socketappender connection to display in its own tab in Chainsaw, use PROP.log4j.remoteSourceInfo as the tab identifier (note the log4j. in front

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
appenders as you describe (we have access to the log4j.properties file on the server)? Thanks for being patient and walking me through all of this. You've easily save me a couple of days of bumbling around trying to get this to work. Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 3