Try SuperLogging of Super from http://www.acelet.com
It is a centralized logging in chronological order.
I do not think that JMS can guarantee the logging is chronological.
JMS has over head as well, comparing to "direct" mechanisms.
--- Shiraz Wasim Zaidi <[EMAIL PROTECTED]> wrote:
> I was wondering what are different design strategies to achieve efficient
> centralized logging of application messages (Exceptions, info etc.) in a
> clustered environment.
>
> What i can think of is having a Messsage driven bean that consumes messages
> from EJB and writes to a
> db table. Thus achieving scalablity/high performance due to asynchronus
> delivery i.e ejb thread does
> not gets blocked for the processing and centralization as db table is a
> shared resource.
>
> Any ideas...
>
> Thanks
> Shiraz
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
