If your Chainsaw config file includes an appender, the appender will process
events received by Chainsaw (for example, a fileAppender hooked up to Chainsaw
would write any events received by Chainsaw to the log file, and you probably
don't want that to happen)..
For Chainsaw to read log files, you need to add a LogFilePatternReceiver to the
config file.
Here's the example from the sample config:
<plugin name="LogFileReceiver"
class="org.apache.log4j.varia.LogFilePatternReceiver">
<param name="fileURL" value="file:///c:/sample.log"/>
<param name="timestampFormat" value="yyyy-MM-dd HH:mm:ss,SSS"/>
<param name="logFormat" value="TIMESTAMP LEVEL [LOGGER] MESSAGE"/>
<param name="name" value="sampleLogFileReceiver"/>
<param name="tailing" value="true"/>
</plugin>
Chainsaw's config file can have any name, it just needs to be accessible as a
URL (and specified as a URL in the application-wide preferences screen)
Scott
-----Original Message-----
From: Robert Vaessen [mailto:[EMAIL PROTECTED]
Sent: Thu 3/3/2005 9:57 AM
To: 'Log4J Users List'
Cc:
Subject: RE: Chainsaw Configuration
Hello Dirk,
Thank you very much. I am a bit embarrassed that I didn't notice
that on my own.
Do you have any comments on the second part of my question
(configuring Chainsaw to use a Rolling File Appender)? It doesn't seem
to be working for me. I've pasted in my config file below.
Robert
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";
debug="true">
<plugin name="UDPReceiver" class="org.apache.log4j.net.UDPReceiver">
<param name="Port" value="4446"/>
</plugin>
<plugin name="SocketReceiver"
class="org.apache.log4j.net.SocketReceiver">
<param name="Port" value="4560"/>
</plugin>
<appender name="RollingFile"
class="org.apache.log4j.RollingFileAppender">
<param name="File"
value="C:/Nexus/Home/Cimulate/Prototype/Chainsaw.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="100KB"/>
<param name="maxBackupIndex" value="2"/>
<layout class="org.apache.log4j.SimpleLayout"/>
/appender>
<root>
<priority value="debug"/>
<appender-ref ref="RollingFile"/>
/root>
</log4j:configuration>
-----Original Message-----
From: OOMS DIRK [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 03, 2005 11:13 AM
To: 'Log4J Users List'
Subject: RE: Chainsaw Configuration
At the moment you can not specify this "plugin config" as a System
Property,
but you can specify it via the menu "Show Application wide preferences"
and
then "Automatic Configuration URL" (in fact this info is stored in the
file
chainsaw.settings.properties as configurationURL). You can specify this
url
using file, http or ftp.
dirk
> -----Original Message-----
> From: Robert Vaessen [mailto:[EMAIL PROTECTED]
> Sent: donderdag 3 maart 2005 17:07
> To: [email protected]
> Subject: Chainsaw Configuration
>
>
> Hello,
>
>
>
> I am currently configuring my Chainsaw receivers via the
> "You have no Receivers defined." dialog that pops up when Chainsaw
> starts. I have seen the "example Receiver configuration" on Chainsaw's
> Welcome tab and from it infer that I can place a configuration file
> somewhere and have Chainsaw load it. But, try as I may, I cannot
> discover how to do this. I know how to do it with Log4j, but I am
> confused with regards to system options and class paths when
> it comes to
> Java Web Start (which is how I am running Chainsaw).
>
>
>
> So, my questions are:
>
>
>
> 1) With what name and in what location can I create a
> Chainsaw configuration file?
>
> 2) Can I, as the example implies, configure Chainsaw's
> internal logging system via this file? More specifically, can I
> configure a Rolling File Appender that aggregates the logging events
> from all of my remote appenders.
>
>
>
> Thank you for your time and consideration.
>
>
>
> Best Regards,
>
> Robert Vaessen
>
>
---------------------------------------------------------------------
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]
