I have implemented such functionality using JMS. In which there is a queue
which all the messages from all the servers and there is a listener to the
queue which receives all the messages and writes that to a text file(rather
than to a database). This is quite efficient as you don't have to have a
diffrent program to read the database to see the messages.
<vendor>
But one problem is while using JMS with weblogic5.1.0 is that the JMS is not
clusterable, but it is clusterable in weblogic6.0
</vendor>
Another option is to use RMI. But that is quite slow.
Rajan
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Shiraz Wasim Zaidi
Sent: Tuesday, March 13, 2001 1:18 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".
