It is an extremely bad idea (as I've already discussed in earlier posts). JBossMQ uses log4j internally so you are just going to get loops and deadlocks in the logging.
logger -> appenders -> jbossmq -> logger -> appenders -> jbossmq and appender -> logger is a deadlock situation in log4j anonymous wrote : | Is there a better forum to post this question on? | The log4j list. I know Ceki was working on a fix for the deadlock issue a while ago. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888492#3888492 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888492 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
