JMSAppender

["Mathew, Bindhu" <Bi...@ssa.gov>]

  Could someone explain a scenario where JMS is useful in logging? 
Thanks,
BMathew

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: JMSAppender

[Steve Ebersole <st...@austin.rr.com>]

The project I am working on is using JMS for logging.  The project happens
to be distributed.  We chose JMS (although really sockets, RMI, JINI, etc
are all valid for the same reasons) because it gave a single/central point
from which to control logging for all the various tiers.  This way logs can
all be stored on a single servers as opposed to whichever server happens to
be running the class requesting the logging.

That being said, I don't know that I would use the log4j JMS stuff as is
without modification/customization.  To be fair, I haven't tried using it,
but have been looking through the code over the last few days.  From what I
have seen of it, it uses a single connection for all log requests.  From my
experience with JMS, this is extremely inefficient and slow; and an approach
which is generally refactored into a pool concept.

HTH

----- Original Message -----
From: "Mathew, Bindhu" <Bi...@ssa.gov>
To: <lo...@jakarta.apache.org>
Sent: Monday, December 17, 2001 12:22 PM
Subject: JMSAppender


>
>   Could someone explain a scenario where JMS is useful in logging?
> Thanks,
> BMathew
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>