The two best options for centralized logging from within a J2EE app will be
either the socket-based appenders or the JMS-based appenders. Both will let
you send the logs to a centralized location and deal with them there.
The JMS approach is reliable because it is using the JMS protocol, however
this reliability comes with a price in terms of the JMS overhead. But it is
ideal if you need logging to be either transactional or never-ever lost.
The socket approach is faster, bu the best of the socket approaches (from a
j2ee perspective) would be the SocketHub approach which can drop messages
under certain circumstances.
It all depends which ones strenghts are the most important to you....
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]
|Sent: Friday, April 04, 2003 12:17 AM
|To: [EMAIL PROTECTED]
|Subject: log4j in clustered j2ee environment.
|
|
|
|Hi,
|
|I want to have centralized logging in J2EE clustered environment.
|
|Anybody have done this before ?
|
|I am trying to understand how it can be done and issues
|related to it, before i
|start.
|
|what is the impact on performance ?
|
|TIA
|Shahaji
|
|
|-----------------------------------------------------------
|----------
|To unsubscribe, e-mail: [EMAIL PROTECTED]
|For additional commands, e-mail: [EMAIL PROTECTED]
|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
