If to
achieve synchronous writing of the logs via an MDB, you will have to configure
the container to only consume one message at a time from the
queue/topic. This could become a bottlekneck and you would run the risk of
overflowing the queue and never catching up. If you bring JMS into the
picture, you will be working against the grain to try to implement synchronous
behaviour.
-----Original Message-----
From: Peter Luttrell [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 12:21 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] JMS vs ASYNC Log4J AppenderWe 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? In the past someone mentioned that the ASYNC appender can deadlock. Has anyone else experienced this? When it deadlocked, what happened? Did log messages just stop getting delivered, or did it take the whole server down? thanks. peter
