I'm sure you get this a lot but after reading quite a few posts I am
still kind of confused:
The lineage between the 1.3 and 1.2 branches is very hazy. From what
i can tell 1.3 is essentially dead and that 1.2 is the recommended
version to use.
As for chainsaw, should I be using the v2 that is available directly
on apache's web site? This appears to be based on version 1.3 code if
I read correctly. Should I instead be using version 1.2.15 and using
the chainsaw client available from there as well as using log4j 1.2.15
on my appender side? I've seen posts mentioning getting the latest
1.2.15 version from svn to get the "right" version of chainsaw. Is
that now current with the latest release or do I still need to tread
into the waters of a nightly build?
On the back porting effort, what is the status there? Is that
completed and that is the purpose of 1.2.15? Is that just a partial
back-port with more to come? Is that a partial back-port and that's
the end of the road?
And finally we have a third party app we were trying to get logging
working under that is using 1.2.9. Could we safely drop in 1.2.15 and
be able to configure our 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, 2008, at 3:52 PM, Scott Deboy wrote:
SocketHubAppender doesn't have the 'application' property support
built
into the appender like 1.2.15 socketappender does, so to use the
application property with sockethubappender, you'd have to:
- use log4j 1.2.15 on the appender side
- also include the receivers companion in the classpath
- specify a rewriteappender which adds the 'application' property and
forwards events to the sockethubappender
I haven't tested that, but it should work..
Btw, log4j 1.3 sockethubappender supported a 'buffersize' param which
would forward the last X events to the connecting sockethubreceiver,
but
it doesn't look like that was back-ported to log4j 1.2.15.
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 503.222.0185
[EMAIL PROTECTED]
www.comotivsystems.com
-----Original Message-----
From: Jason Tholstrup [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2008 12:57 PM
To: Log4J Users List
Subject: Re: Chainsaw Tab identifier
Sorry Scott I had not tried your instructions before I replied last
time.
I can get PROP.log4j.remoteSourceInfo to show up in my tab identifier
but PROP.application does not seem to work (which to be honest is much
closer to what I want). I've seen that there is an issue with the
serialized object translation from the 1.2.X branch to the 1.3 based
chainsaw v2 download, and I don't receive Class, Method, File, or Line
information in my logs. Is this possibly the reason PROP.application
does not show up, or is there something else I have missed?
Here is the log4j.properties snippet for my app. I've bounced my
server container just to make sure it reloaded and PROP.application
continues to return nothing in chainsaw
log4j.properties sinppet (on server)
log4j.appender.HUB=org.apache.log4j.net.SocketHubAppender
log4j.appender.HUB.port=9005
log4j.appender.HUB.LocationInfo=true
log4j.appender.HUB.Threshold=DEBUG
log4j.appender.HUB.application=SES
Test Tab identifier string
PROP.application - PROP.log4j.remoteSourceInfo
chainsaw.xml
?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration>
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";
debug="true">
<plugin name="SocketHubReceiver"
class="org.apache.log4j.net.SocketHubReceiver">
<param name="host" value="devocs.theebsgroup.com"/>
<param name="port" value="9004"/>
<param name="reconnectionDelay" value="30000"/>
<param name="name" value="devocs SES"/>
</plugin>
<root>
<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 of the property name - log4j. isn't some special
property name, that's just the name of the property).
2. The 'application' property on socketappender is how you route
events
to different tabs when the two apps are running on the same server
and
using socketappender.
Here's an example of that config:
<appender name="SOCKET"
class="org.apache.log4j.net.SocketAppender">
<param name="remoteHost" value="localhost"/>
<param name="LocationInfo" value="true"/>
<param name="port" value="4560"/>
<param name="application" value="someappname"/>
</appender>
Use a different value in the 'application' param for each of the
socketappender configs and you should be fine.
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 503.222.0185
[EMAIL PROTECTED]
www.comotivsystems.com
-----Original Message-----
From: Jason Tholstrup [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2008 9:24 AM
To: log4j-user@logging.apache.org
Subject: Chainsaw Tab identifier
Hello,
I'm trying to figure out what things I need to place in my Tab
identifier field to filter out my applications. I'm using log4j v
1.2.13 and chainsaw v2. I have two applications running on the same
server and both are using a socketHubAppender on different ports.
I don't have any location info so the default "PROP.hostName -
PROP.application" only separates by hostname and since I'm running
two
apps on the same server I get both logs dumped to the same tab. I've
tried adding PROP.remoteSourceInfo (since that is a column in the
logs
that shows up and has the port number listed) and that property
appears to return nothing. It's my understanding that the location
info does not work in log4j 1.2.X. So my question is two fold. Is
there some reference that I can look at that will tell me what
properties are available, and can someone tell me how I would go
about
doing this? I see in the comments for LoggingEventFieldResolver the
following field are available but nothing here seems like it will
work
for me. Plus there seems to be no explanation of what keyName is in
PROP.keyName.
* Field Name Field value (String
representation Return type
* LOGGER category name
(logger) String
* LEVEL
level Level
* CLASS locationInformation's class
name String
* FILE locationInformation's file
name String
* LINE locationInformation's line
number String
* METHOD locationInformation's method
name String
* MSG
message Object
* NDC
NDC String
* EXCEPTION throwable string
representation ThrowableInformation
* TIMESTAMP
timestamp Long
* THREAD
thread String
* PROP.keyName entry in the Property
hashtable String
* mapped to the key [keyName]
Any help would be appreciated.
Jason Tholstrup
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
