RE: Asynchronous logging ? JMSAppender ?

[Veerappan Saravanan]

Title: Asynchronous logging ? JMSAppender ?

When using JMS, if these messages are something that you cannot loose under any circumstances, then you would have to use persistence JMS, which affects performance and would most likely be an over kill depending on where you log these messages.

 

Van

-----Original Message-----
From: Jamie Tsao [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 3:58 PM
To: [EMAIL PROTECTED]
Subject: Asynchronous logging ? JMSAppender ?

Hi,

I would like to asynchronously log messages (for performance reasons).  I know the AsyncAppender is designed for this purpose, but I believe there have been performance measures that don't necessary prove the case.  I was also thinking that I could use a JMSAppender.  Now, I know that this is not truly asynchronous, because each logging request is not actually performed in a separate thread.  But since performance is usually degraded due to IO (i.e. writing log to a file), this solution may still be somewhat asynchronous.  I would have a receiver (working in a separate thread) that takes messages off the queue and writes them to a log file (or NT Event log, etc.). 

My question is ... is this overkill ?  Does anyone have experience with a logging system which uses JMS in the manner specified above ?  I'm worried that the management of messages on the queue might outweight the benefits.  Perhaps the AsynchAppender is the better/appropriate approach ?

Any ideas ?

Thanks,

Jamie

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]