The more appenders/receivers the better.. The JMDNS (Java implementation of zeroconf/rendezvous/bonjour) option may work well for you, as would a well-known multicast group using multicastappender/receiver.
Paul wrote a ZeroConfSocketHubAppender - and it will work with log4j 1.2.x. Here's a viewcvs link to a page Paul wrote that describes log4j zeroconf support: http://svn.apache.org/viewcvs.cgi/logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html?view=markup You can find more info on JMDNS at http://jmdns.sourceforge.net/ Paul, any comments? Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: Sam Preston [mailto:[EMAIL PROTECTED] Sent: Wed 2/1/2006 9:43 AM To: Log4J Users List Subject: Re: logger as a Jini service? Hi Scott, Thanks for your recommendations. I'm currently using SocketHubAppenders, but it means that I have to know which computers I'll be running loggers on. I'm working on applications for a sample 'interactive workspace', a room with hardware and software infrastructure for users coming and going with their laptops, etc., and collaborating with each other. The reason I'd like to use Jini is so when an application is started on the local network, it could automatically register itself, and my central logging application could immediately start receiving logging events from it, without having to know what computer it is running on. Has anyone else addressed this problem in a different way? I'm already using Jini services for other applications, so this was the first solution that came to mind. If no one else has a better idea, I may end up writing my own AppenderService (an appender as a Jini service)--would anyone else be interested in something like that? Thanks again, -Sam On 2/1/06, Scott Deboy <[EMAIL PROTECTED]> wrote: > Not as a Jini service. > > How do you want to monitor them? > > If you'd like to use Chainsaw, there are a few options based on if you are ok > losing messages or not, and if you're in an environment that can send/receive > multicast/udp packets. > > Multicast/udp: > - Use the recently-added support for JMDNS in Chainsaw (thanks Paul) > - Use multicastappender (requires log4j 1.3 alpha on the appender side) and > multicastreceiver on a well-know multicast address > > Reliable (files/database): > - Log to a database (DBAppender or custom logging) and use DBReceiver or > CustomSQLDBReceiver) > - Use udpappender (log4j 1.3 alpha on appender side) and udpreceiver > - Use SocketHubAppender on each machine and have multiple plugin entries in > the Chainsaw config, one sockethubreceiver for each machine > - Write to a log file on each server and use multiple LogFilePatternReceivers > or VFSLogFilePatternReceivers if logs are accessible via ssh) > > I'm sure there are other ways but these are a few. Hope this helps. > > Scott Deboy > COMOTIV SYSTEMS > 111 SW Columbia Street Ste. 950 > Portland, OR 97201 > > Telephone: 503.224.7496 > Cell: 503.997.1367 > Fax: 503.222.0185 > > [EMAIL PROTECTED] > > www.comotivsystems.com > > -- -------------------- J. Samuel Preston Research Associate Center for Advanced Engineering Environments Old Dominion University Research Foundation --------------------------------------------------------------------- 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]
