Paul, Thanks for introduction to a great tool. Okay, this is the situation that I am in....We have a huge application which is already using ActiveMQ and 'the powers that be' want to go the ActiveMQ route. Having said that Chainsaw seems to be a wonderful tool, so I shall try and pass that along after testing it. All I want at this point is a very simple class file producing a simple INFO kind of log message and sending it a queue and then another simple class file taking it out of the queue and displaying it. I am trying to follow the example of a ProducerTool and ConsumerTool, will let you know how it goes....:). Thanks again for some very useful guidance.
Regards, -Misty. On 6/27/07, Paul Smith <[EMAIL PROTECTED]> wrote:
On 28/06/2007, at 11:31 AM, Misty Thornton wrote: > Paul, > > Yes, all I need is an application using JMSAppender to send log > messages to > a message queue and then another application which can consume these > messages and make them 'viewable'. I have got the SMTPAppender part > working, > which sends my 'error' logs using email...:). Just struggling with the > JMSAppender part..Thanks for all your help. are you _really_ tied to JMS? Could it just be a relatively simpler socket-based implementation? If it could, then you should just use Chainsaw: http://logging.apache.org/log4j/docs/chainsaw.html Chainsaw can connect to a remote application and capture it's logs. It actually _can_ use JMS, but I'm not convinced you really need that transport mechanism when a Socket is all you need to use. I would try out Chainsaw and configure your application like this: * inside your application, configure a SocketHubAppender. This will create an appender that allows other clients to connect to it and receive Logging events * Start Chainsaw, and configure a SocketHubReceiver and point it at the host where your application is running. It will then connect and you'll receive all your lovely Logging events in a nice viewer. Paul
