When it deadlocked, what happened? Did log messages just stop getting delivered, or did it take the whole server down?

Has one else experiences such a problem?

.peter

Juha Lindfors wrote:
I've seen the async appender deadlock, so I'm not entirely
convinced of its robustness. I did not pursue it any further to find the
cause. There's at least one open bug in the log4j tracker for this.

YMMV

-- Juha

On Fri, 19 Dec 2003, Peter Luttrell wrote:

  
We log a ton of stuff and are having problems caused by synchronous logging
blocking the appserver when linux rotates other various logs in the
system. So we're considering using the ASYNC or JMS appenders. If we use
the JMS appender we'll write a quick MDB to log all messages synchronously.

Does anyone have any experience with these appenders in a high volume? Are
there things to watch out for with either?

Are there any key advantages or disadvantages of using JMS vs ASYNC? The
obvious one is that JMS is sent to a topic so we'd have control over what
we do with the log messages.

Is there much more overhead with JMS vs ASYNC?

thanks.
.peter
    




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
  

Reply via email to