[jboss-as7-dev] Adding more trace level logging

[David M. Lloyd]

On 03/23/2011 04:18 PM, Scott Stark wrote:
> One example location is in the
> org.jboss.as.server.Bootstrap.Configuration inner class, which has no
> logger. I need to know what the absolute path to the standalone.xml file
> is that the server is trying to load. So, is there a pattern to where we
> are allowing loggers vs Stdout?
>
> It looks like the logger categories are more along the lines of
> subsystem names rather than simply using the class name which is
> embedding the logger. Any usage guidelines to follow for that?

The logger names are typically related to what process is being 
debugged.  For example if you're creating a logger in the AS server 
module and the logger relates to bootstrap, you might use the 
"org.jboss.as.server.bootstrap" logger, or a sublogger thereof.

That said, loggers are allowed pretty much anywhere.  However take 
caution before adding many INFO/WARN/ERROR messages because every one of 
these has to be internationalized.  DEBUG and TRACE do not.

> On 3/23/11 2:03 PM, Scott Stark wrote:
>> With the problems with the debugger crashing the server vm, I'm finding
>> I need to add a lot of trace level statements to both the AS and
>> components to try to figure out why things don't work. What is the best
>> way to get these additions back into the AS codebase at least?
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
- DML