RE: log4j LoggingEvent repeater

["Bradley, Todd" <to...@Polycom.com>]

Through trial and error, I think this problem was due
to incompatibilities between log4j 1.2.8 and Chainsaw
v2.  I'm guessing that Chainsaw saw location information
in the LoggingEvents and dropped its connection to the
application's SocketHubAppender.  Then, they reconnected
and the same thing happened again, over and over.

Anyhow, I ended up having to write my own code for the
LogEventRepeater I needed.  SimpleSocketServer didn't
do exactly what I needed, and the underlying SocketNode
didn't, either.  In my case, due to this apparent incom-
patibility, I needed a SocketNode that would filter out
location information, plus I needed something like a
SimpleSocketServer that would allow you to specify the 
IP address on which to listen for connections (for run-
ning on a machine with multiple ethernet interfaces).

But, it's all working nicely now, and I and the rest of
my team are able to use Chainsaw v2 to monitor our
application that's running on its own private network
(with one gateway machine between it and us, which is
where the LogEventRepeater runs).

Chainsaw v2 really is a big improvement over v1!  I
can't wait for it (and log4j 1.3) to be ready for
prime time and officially released.


Todd.


> -----Original Message-----
> From: Bradley, Todd [mailto:todd.bradley@Polycom.com] 
> Sent: Thursday, June 30, 2005 3:53 PM
> To: Log4J Users List
> Subject: RE: log4j LoggingEvent repeater
> 
> Thanks.  That was the answer I was looking for.
> It does appear to do close to what I wanted.
> However, I can't get the darn thing to work.
> I turned on log4j.debug and now see that it's going into a loop of
> 
> log4j: dropped connection
> log4j: accepting connection from ...
> log4j: dropped connection
> log4j: accepting connection from ...
> 
> I'm trying to use Chainsaw v2 as my client app, and I already 
> found the notes about not sending any location information, 
> which I'm not doing.
> 
> Any other ideas why the SimpleSocketServer would accept and 
> then immediately drop connections?
> 
> 
> Todd.
> 
> 
> > -----Original Message-----
> > From: Ceki Gülcü [mailto:listid@qos.ch]
> > Sent: Thursday, June 30, 2005 10:37 AM
> > To: Log4J Users List
> > Subject: RE: log4j LoggingEvent repeater
> > 
> > Todd,
> > 
> > Try org.apache.log4j.net.SimpleSocketServer. I believe it 
> does exactly 
> > what you want.
> > 
> > At 06:21 PM 6/30/2005, Bradley, Todd wrote:
> > >I probably won't be allowed to put JBoss on the intermediate
> > machine,
> > >although it does have a JRE.  So I was hoping for a smaller,
> > more self
> > >contained solution.  Any other ideas?
> > >
> > >
> > >Todd.
> > 
> > --
> > Ceki Gülcü
> > 
> >    The complete log4j manual: http://www.qos.ch/log4j/
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
> 
> 

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