I can verify that I can connect to a log4j1.2.8 app-server via Chainsaw v2 via a SocketHubAppender/Receiver combo. SocketHubAppender is definitely included in 1.2.8 and there has not been much modification to it for 1.3 (just some tidy up, from what I can see in the cvs history) Cheers, Paul Smith
> -----Original Message----- > From: Scott Deboy [mailto:[EMAIL PROTECTED] > Sent: Friday, July 23, 2004 2:20 AM > To: Log4J Users List > Subject: RE: Configuration Question > > The options I described previously are only available to folks using the > CVS head version of log4j (socketHubAppender and receiver aren't > available in log4j 1.2.8). > > If you need to use 1.2.8 on your app server, this should work (but I > haven't tried it): > > Configure the app server to send events by SocketAppender to a different > machine. This second machine would use the CVS head of log4j, running > SimpleSocketServer. SimpleSocketServer's configuration file would > include a SocketHubReceiver configuration to receive events from the app > server, as well as a SocketHubAppender to support connections from > clients. > > Scott > > > -----Original Message----- > From: Scott Deboy > Sent: Thursday, July 22, 2004 9:06 AM > To: Log4J Users List > Subject: RE: Configuration Question > > > If you configure your app server to send events using a > SocketHubAppender, any number of clients can connect to the server and > receive events via SocketHubReceiver. > > There are also ways to transfer this processing off of the app server by > using a SimpleSocketServer on a separate machine. Set up this new > machine using SimpleSocketServer with a SocketHubReceiver configured to > connect to the app server's SocketHubAppender. > > Clients like Chainsaw would connect to the new machine's > SocketHubAppender using SocketHubReceiver to receive events. > > You could also set up the app server to send events to the > SocketHubAppender via AsyncAppender, but read the Javadoc for > limitations (AsyncAppender uses a bounded buffer, so you could lose > messages). > > Other non-tcp based options (if you can use the CVS head of log4j) > include the new MulticastAppender/Receiver pair and UDPAppender/receiver > pair. These are UDP-based and you could lose messages. > > Also, the CVS head version of socketHubAppender supports a > size-configurable cyclic event buffer. Clients connecting to the > socketHubAppender will receive the most recently received X number of > events as specified by the bufferSize param. > > See the javadocs for information on these appenders and receivers. > Here's a link to the ViewCVS org.apache.log4j.net package, which > contains these appenders/receivers. > > http://cvs.apache.org/viewcvs.cgi/jakarta-log4j/src/java/org/apache/log4 > j/net/ > > Hope this helps, > > Scott > > -----Original Message----- > From: Perry, Mike [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 22, 2004 5:06 AM > To: Log4J Users List (E-mail) > Subject: Configuration Question > > > Hi everyone, please forgive my ignorance for asking the obvious, here is > what I am attempting to do: We are running the IBM WebSphere > Application Server, v4.0, on an iSeries box. Our applications will log > to > multiple files and utilize the socket appender to send specific errors > to > Chainsaw v2. What I would like to know is, how can I set up Chainsaw > V2 on > a client and have the errors reported to Chainsaw from the application > server. The client will have JDK 1.4 on it. Does chainsaw have a > configuration file that needs to be modified to communicate with a > server? > > > again please forgive my ignorance, I am brand new to logging and > chainsaw. Any advice or examples would be greatly appreciated. > > Mike Perry > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
