Hi
Justin Forder wrote:
> Carlos Valiente <[EMAIL PROTECTED]> wrote:
>
> >Is there any way to configure logging verbosity?
>
> To get rid of the JAWS trace, I'm afraid you need to alter a compile-
> time flag and recompile. It's the debug flag in JDBCCommand.java.
>
> If someone explains how to configure logging at run-time, I shall change
> the JAWS code to use a combination of compile-time and run-time flags
> (compile-time is the only way to completely remove the performance
> overhead).
Two things here: log production and consumption. Log production is up to
your code, but the consumer (ConsoleLogging for example) can be set to
filter out a certain producer, or particular log messages.
In conf/jboss.conf:
<MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error">
<ARG TYPE="java.lang.String" VALUE="[{2}] {4}">
</MLET>
This will include all types of messages. Change to:
<MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="Error">
<ARG TYPE="java.lang.String" VALUE="[{2}] {4}">
</MLET>
..and you will only see errors.
the FileLogging also takes parameters for filtering out particular
sources. I see now that ConsoleLogging cannot do this. I will fix this.
Also, currently the log messages production is done through JMX, and the
JMX RI creates *one new thread for each message*. So, when the final JMX
RI is released which does not do this, performance for logging will
automatically be improved.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
