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: Chainsaw issue
Date Wed, 17 Dec 2008 16:38:38 GMT
By default, Chainsaw stores events in each tab in a cyclic buffer (5000 entries).  If you're
getting events really fast, they could drop out of the cyclic buffer. 

I don't know of another reason (other than an out of memory error) that would cause this.

Look in the chainsaw-log tab for errors.  Also, enable your java console (or run Chainsaw
from the bundle download) to see if you're getting an uncaught exception.

If so, please submit a bug.


Scott Deboy
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185



-----Original Message-----
From: Amol Fuke [mailto:amol.fuke@tcs.com]
Sent: Wed 12/17/2008 3:19 AM
To: log4j-user@logging.apache.org
Subject: Chainsaw issue
Hi , 

I an using chainsaw for seeing the jboss logs.In my application , when we 
try to login by putting wrong password , ldap throws one exception which 
has  a null value in it.
While looking into the chainsaw logs , it shows some logs with nulls , but 
after some appearances it just gives up and does not show up anything.

Do you know why this happense ? any known issue ? or any alternative tool 
to chainsaw ?

Let me know.

Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

View raw message