DBAppender and connection pooling

2008-02-26 Thread Andreas Grund
Hi mailinglist, I have another question about the DBAppender: Is there any reaon, why the appender creates for every log message a new connection and new prepared statements? It may speed up the appender, if both can be pooled... Is the WatchDog may be the reason? So that changes in my

Log level problems

2008-02-26 Thread Adrian Mitev
Hi all! I want to display in the console only INFO messages but for one log level to display the DEBUG messages. Here is my log4j.xml appender name=CONSOLE class=org.apache.log4j.ConsoleAppender errorHandler class=org.jboss.logging.util.OnlyOnceErrorHandler/ param name=Target

Re: Different levels to different appenders

2008-02-26 Thread Mikael Ståldal
Paul Smith skrev: If this truly is what you want, Are you implying that it would be a bad idea? Why would it be a bad idea? then set the logger levels for both hierarchies to DEBUG, and write yourself a simple custom Filter implementation that accepts/denies events based on your logic, and

RE: Log level problems

2008-02-26 Thread Bender Heri
Adding the additivity attribute should do the trick: category name=org.jboss.ejb.plugins.cmp additivity=false BTW: the name category is deprecated. Use logger instead. Your cited configuration does not declare the referenced appender FILE. Heri -Original Message- From: Adrian

Re: Different levels to different appenders

2008-02-26 Thread Paul Smith
On 27/02/2008, at 12:51 AM, Mikael Ståldal wrote: Paul Smith skrev: If this truly is what you want, Are you implying that it would be a bad idea? Why would it be a bad idea? Why not simply have all the events your interested in together, in context, in one log file? Have one File