Scott, not sure that I follow you when you say, "pushed Chainsaw to your own 
web server."  Do you mean try to create my own JNLP file?

From: Scott Deboy [mailto:scott.de...@gmail.com]
Sent: Thursday, January 17, 2013 3:06 PM
To: Log4J Developers List
Subject: Re: Chainsaw v2 Log viewer

Hi Jason,

Glad that helped - there are a lot of new features - feedback welcome.

The latest developer snapshot isn't available via webstart, but if you pushed 
Chainsaw to your own web server, yes, the first arg Chainsaw accepts is a URL 
to a configuration file (you can use this feature to create different aliases 
in Windows etc.).
Scott

On Thu, Jan 17, 2013 at 3:00 PM, Stein, Jason 
<jason.st...@vertexgroup.com<mailto:jason.st...@vertexgroup.com>> wrote:
Thank you, Scott, that worked great.  Now my next wish is this:

Since I have about 50 Test/QA JBoss environments, to use JNLP to start Chainsaw 
and have the appropriate configurations automatically loaded for each 
environment, depending upon which jnlp link one clicks.

Is that possible?

From: Scott Deboy [mailto:scott.de...@gmail.com<mailto:scott.de...@gmail.com>]
Sent: Thursday, January 17, 2013 1:55 PM
To: Log4J Developers List
Subject: Re: Chainsaw v2 Log viewer

Latest developer snapshot is available here: http://people.apache.org/~sdeboy

On Thu, Jan 17, 2013 at 1:55 PM, Scott Deboy 
<scott.de...@gmail.com<mailto:scott.de...@gmail.com>> wrote:
If you aren't already, I'd suggest trying the latest developer snapshot.
It has built-in support for generating a Chainsaw configuration from a 
fileappender/conversionpattern:
 - File, load Chainsaw configuration menu
 - Use fileappender entries from a log4j config file (can be .properties or 
.xml)
 - Select the  'open file' button and browse to your log4j configuration file 
containing the fileappender entries
 - Optionally select 'always start Chainsaw with this' and probably 'Save 
configuration as'
Let me know if that doesn't work.
If you are having problems, you can always use 'MESSAGE' as your logformat, 
which will not parse the line at all, just write the entire line to the 
'MESSAGE' field.

Scott

On Thu, Jan 17, 2013 at 1:42 PM, Stein, Jason 
<jason.st...@vertexgroup.com<mailto:jason.st...@vertexgroup.com>> wrote:

I'm trying to get Chainsaw up and running with our Jboss application.  We're 
currently using a JBoss log4j log which has a conversion pattern that looks 
like this:

<param name="ConversionPattern" value="%d{DATE} %-5p [%c{1},%X{host}] 
[%-10X{username}][%t] %m%n"/>

As a result of not knowing exactly what logformat to use for this, I was 
getting a message which stated that there were no matching lines, and then it 
would show the log message that wasn't matching.

Then, in order to get Chainsaw to work, I created a separate conversion pattern 
(in a separate appender) which was detailed in your tutorial like this:

<param name="ConversionPattern" value="%d %-5p [%t] %C{2} (%F:%L) - %m%n"/>

And used the logformat of TIMESTAMP LEVEL [THREAD] CLASS (FILE:LINE) - MESSAGE
Like I said, hoping to simply get something in the chainsaw-log...

All I'm getting is messages that say "no further lines to process", rather than 
any real log messages.  As a matter of fact, I don't see ANY real log messages, 
just chainsaw-logs.

What I was hoping I could do was use Chainsaw as a better log viewer - instead 
of using TextPad or Notepad++ .

Any help would be very much appreciated.




Please consider the environment before printing this email.
The information contained in this e-mail and its attachments are confidential 
to the intended recipient and may be legally privileged or otherwise protected 
from disclosure. If you have received this message in error,you must not print 
this email or its attachments. Please notify the sender immediately and delete 
the message and any attachments from your computer. The unauthorized use, 
disclosure, copying or alteration of this message is forbidden. Emails are not 
secure and may contain viruses. Vertex accepts no responsibility for viruses; 
it is your responsibility to scan or otherwise check this email and any 
attachments.


Reply via email to