Bugs item #653047, was opened at 2002-12-13 01:34
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=653047&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Sebastian Hauer (hauer)
Assigned to: Nobody/Anonymous (nobody)
Summary: log4j .isDebugEnabled() will return true

Initial Comment:

After doing some testing I found out that no matter
which class I used to obtain a log category, either
"org.apache.log4j.Category", "org.apache.log4j.Logger"
or "org.jboss.logging.Logger"  once I did a:

log.isDebugEnabled() 

it would always return true.

Though as I logged with:

log.debug();

it would not show up in the log output. So the internal
check in debug() seems to work fine. 

I also tested whether "org.jboss.logging.Logger"
isTraceEnabled() behaves that way. But it does not. It
would return false as expected.

If I run a standalone application with log4j output
isDebugEnabled() will actually work as expected.

Attached you will find a little test case with 3 MBeans
distributed as source with a little ant build file.
The build will create a .sar file that can be deployed
into jboss.
I did only test on 3.0.4 so far.

I hope this was the right bug category.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=653047&group_id=22866


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to