I apologize for not re-stating my original issues with the socket stuff. There is no way to pass in some sort of information as far as where the log message is coming from unless people use package names (which is something I can't control or enforce). I could extend off of the log4j stuff and attempt to do so but that's not a solution we would like to resort to if jms can get the job done.
Right now I'm getting ready to test sending messages via jms to jboss. Now I just need to figure out how to write something to handle the jms topics on the jboss side. I would appreciate any more input you can provide on jms! -----Original Message----- From: Kaufman Ng [mailto:[EMAIL PROTECTED] Sent: Friday, June 24, 2005 10:07 AM To: Log4J Users List Subject: RE: Spam:Log4j and JMS Either JMS or socket connections would do. For JMS it's a little trickier to set up (depending on your JMS provider). I have implemented the JMS receiver using activeMQ and uberMQ. For socket connections you can use SocketAppender. On the receiving end there's a choice of SocketNode and SocketServer. Hope this helps. Kaufman Ng -----Original Message----- From: Schuweiler, Joel J. [mailto:[EMAIL PROTECTED] Sent: Thursday, June 23, 2005 4:27 PM To: 'Log4J Users List' Subject: Spam:Log4j and JMS While I don't know much about jms would this perhaps be a route to take for logging to different files on a remote machine from a cluster full of many applications? --------------------------------------------------------------------- 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]
