jboss 4.0 support about javamelody HOT 13 CLOSED

jboss 5.1 does not have this problem.

The stack trace seems very truncated. Is there some more ?

Can you check if you have more than one log4j-x.x.x.jar in your app and jboss 
server ?
If you have just one, please try to update it to a newer version.

And if someone starts jboss 4.0, with a webapp including javamelody please say 
it to us.

Thanks.

I made a test with a test webapp including javamelody (trunk of today) in jboss 
4.0.5
It worked well as seen in joined screenshot. And there was no problem with 
Log4J.

I think that your issue could come from what is included in your webapp or from 
how
your webapp and log4j are initialized.
Somehow jboss 5.1 fixes that.

So I changed the status of the issue to invalid, because not reproducible.
Please reopen the issue if you have more informations or if you can give a test 
case
like a webapp to reproduce the issue.
Thanks

[deleted comment]

[deleted comment]

[deleted comment]

[deleted comment]

Testing 1.12.0, this logging issue no longer seems to occur.

[snip previous comment, had details not related to this]

ok, thanks for the information