WRT to asynchronous messaging for logging. I generally like my messages
logged in chronological order to the destination. Using asychronous
messaging in a clustered environment, and not many servers allow a topic to
span multiple nodes in a cluster I believe, I don't think can guarantee that
your messages will be written chronologically. From database records this is
less of an issue than for flat files.
Is it typical to log asychronously? I understand why but has the overhead
from logging been significally reduced as a result?
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Shiraz Wasim Zaidi
> Sent: Monday, March 12, 2001 11:48 PM
> To: [EMAIL PROTECTED]
> Subject: Logging in a clustered environment
>
>
> 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".
>
===========================================================================
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".
