logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: Save Chainsaw State
Date Mon, 08 Nov 2004 17:29:56 GMT

as well as an ORO jar if you want to use the 'like' rule (regexps) in Chainsaw expressions

You can specify the config file in the command line instead of setting it in the app preferences.

Here's the command line I'd use (all jars in the current directory):

java -Dlog4j.configuration=c:\downloads\jboss-chainsaw.xml -classpath log4j-1.3alpha0.jar;log4j-chainsaw-1.3alpha0.jar;jakarta-oro-2.0.8.jar

Let me know how this works work for you.


-----Original Message-----
From:	Oleg Lebedev [mailto:oleglebedev@waterford.org]
Sent:	Mon 11/8/2004 8:07 AM
To:	Log4J Users List
Subject:	RE: Save Chainsaw State

Thanks for the hint. I tried it, but couldn't load your
chainsaw-jboss.xml, which I put in Y:/chainsaw/chainsaw.xml. No
receivers were loaded and I got several warning messages shown below.
Are there any jars that I need to put on my classpath so that chainsaw
can load org.apache.log4j.joran.JoranConfigurator?

What I am trying to do is to chainsaw working from a network drive. I
need multiple users to be able to start chainsaw from the network drive
and have chainsaw load its configuration from an xml file. 

Y:\chainsaw>java -jar log4j-chainsaw-1.3alpha0.jar
log4j:INFO SecurityManager is now: null
Using font=Arial
log4j:ERROR pluginDirectory cannot be null, and it must exist and must
be readab
le, using the normal Classloader
log4j:INFO Using 'file:///Y:/chainsaw/chainsaw.xml' for
log4j:INFO Using 'file:/Y:/chainsaw/chainsaw.xml' for auto-configuration
log4j:INFO  in JP startDocument
log4j:WARN No appenders could be found for logger
log4j:WARN Please initialize the log4j system properly.
log4j:WARN Could not find any local JavaDocs, you might want to consider
 'ant javadoc'. The release version will be able to access Javadocs from
the Apa
che website.
log4j:WARN Failed to locate Receiver
log4j:INFO ORO classes not found - Like rule not supported



-----Original Message-----
From: Scott Deboy [mailto:sdeboy@comotivsystems.com] 
Sent: Friday, November 05, 2004 7:42 PM
To: Log4J Users List
Subject: RE: Save Chainsaw State

Here are instructions and a sample xml config file for use with

Change the xml file to define a 'plugin' for each event source you would
like to view in Chainsaw - socket, file, etc.  You can define as many
receiver plugins as you'd like (this example will load a jboss log

Let us know if you have further questions...


Inside Chainsaw, select:
view-show application wide preferences
- enter the URL of this chainsaw.xml in the 'automatic configuration
URL' field (for example: file:///c:/downloads/chainsaw-jboss.xml)
- restart chainsaw

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> <log4j:configuration
xmlns:log4j="http://jakarta.apache.org/log4j/" debug="true">

   <plugin name="logFileReceiver"
     <param name="fileURL"
value="file:///c:/downloads/jboss/server/default/log/server.log" />
     <param name="timestampFormat" value="HH:mm:ss,SSS"/> 
     <param name="logFormat" value="TIMESTAMP LEVEL [LOGGER] MESSAGE"/> 
     <param name="name" value="jboss-log-file" />
     <param name="tailing" value="true" /> 

      <level value="debug"/>

-----Original Message-----
From:	Oleg Lebedev [mailto:oleglebedev@waterford.org]
Sent:	Fri 11/5/2004 3:50 PM
To:	log4j-user@logging.apache.org
Subject:	Save Chainsaw State
I've been using Chainsaw for a couple of weeks and it works great for
me. One thing I cannot figure out is how to save Chainsaw receiver
information and have it loaded the next time Chainsaw is started. I
found a couple of log4j.xml files, which contain plugin definitions for
the receiver, but I don't know where I should put this file so that
Chainsaw can read it when restarted. Any hints would be appreciated.

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

View raw message