Hi,
I suspect the problem is due to a serialization problem for the
LoggingEvent. Chainsaw was built using version 1.1.3 of Log4J. What version
of Log4J is your application that is sending the events to Chainsaw using?
The stack trace produced from Chainsaw would be very helpful in confirming
this.
The current implementation of Chainsaw keeps all the events it receives. So
when this number gets very large (under load, or over time) it will
"cripple". A fix would be to modify Chainsaw to only keep the last XX
events.
Regards,
Oliver Burn
www.puppycrawl.com
> -----Original Message-----
> From: Johnson, Clay [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 13 July 2001 12:40 AM
> To: 'LOG4J Users Mailing List'
> Subject: RE: Socket logging
>
>
> I downloaded chainsaw out of curiosity, and it seemed to cripple
> under large
> load of events. Maybe it wasn't intended for monitoring
> unfiltered streams.
>
> That may not have anything to do with your case, but it indicates that the
> utility of the product is not unbounded.
>
>
> > -----Original Message-----
> > From: Sam Newman [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, July 12, 2001 5:33 AM
> > To: [EMAIL PROTECTED]
> > Subject: Socket logging
> >
> >
> > Hi all,
> >
> > I wanted to create a simple test program to try out the
> > SocketAppender class
> > in log4j. I decided to use the Chainsaw program to view to
> > log events. I
> > created 2 appenders, one console appender, and one socket
> > appender. The
> > socket appender is setup on the same port as chainsaw (in
> > this instance,
> > 1000) and I know this is correct as if I change this port or
> > if I don't
> > start chainsaw the logging program throws an exception. The
> > messages get
> > printed to the console, but I see no messages in chainsaw.
> > Currently I'm not
> > sure if this is a problem with my use of chainsaw, or with my
> > use of log4j,
> > and I was wondering if someone could take a look at my code
> > and see if I've
> > made any obvious mistakes?
> > I get some messages from chainsaw, informing me that its
> > starting to get
> > data (I assume my messages), but it then reports a
> > SocketException (from
> > com.puppycrawl.tools.chainsaw.LoggingReciever). I'm guessing
> > this is mist
> > likely a problem with either chainsaw or my use of it, so
> > will probably
> > build my own version tonight with some more debug info in it.
> > If anyone has an alternate Socket display program I could use
> > to see if
> > Chainsaw is the problem, I'd appreciate it.
> >
> > code:
> >
> > public static void main(String args[]) {
> > Category cat =
> > Category.getInstance(SocketLoggerTester.class.getName());
> > SocketAppender appender = new SocketAppender("localhost", 1000);
> > appender.setLayout(new TTCCLayout());
> > cat.addAppender(appender);
> > cat.addAppender(new ConsoleAppender(new TTCCLayout()));
> > BasicConfigurator.configure();
> > cat.info("Hello!");
> > try {Thread.sleep(5000);}catch (Exception e){}
> > cat.info("Bye!");
> > }
> >
> > Thanks in advance,
> >
> > sam
> >
> >
> > ---------------------------------------------------------------------
> > 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]
