jboss 4.0 support

[GoogleCodeExporter]

1.9.0 javamelody
jboss 4.0.5

relevant error:
09:36:21,387 ERROR [MainDeployer] Could not start deployment: <war>

java.lang.ClassCircularityError: org/apache/log4j/spi/LoggingEvent
    at net.bull.javamelody.Log4JAppender.append(Log4JAppender.java:62)
    at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)


I've been evaluating Glassbox and Infrared for a while, just learned about
javamelody and hope to compare.

Original issue reported on code.google.com by binarymo...@gmail.com on 27 Nov 2009 at 2:41

[GoogleCodeExporter]

jboss 5.1 does not have this problem.

Original comment by binarymo...@gmail.com on 27 Nov 2009 at 5:55

[GoogleCodeExporter]

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

Original comment by evernat@free.fr on 27 Nov 2009 at 6:50

[GoogleCodeExporter]

Original comment by evernat@free.fr on 27 Nov 2009 at 6:50

• Changed title: jboss 4.0 support

[GoogleCodeExporter]

Original comment by evernat@free.fr on 5 Dec 2009 at 11:23

• Changed state: Accepted

[GoogleCodeExporter]

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.

Original comment by evernat@free.fr on 1 Feb 2010 at 11:57

[GoogleCodeExporter]

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

Original comment by evernat@free.fr on 19 Feb 2010 at 10:22

• Changed state: Invalid

Attachments:

• [javamelody jboss 4.0.5 ok.PNG](https://storage.googleapis.com/google-code-attachments/javamelody/issue-6/comment-6/javamelody jboss 4.0.5 ok.PNG)

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by evernat@free.fr on 19 Feb 2010 at 10:32

Attachments:

• [javamelody jboss 4.0.5 ok.PNG](https://storage.googleapis.com/google-code-attachments/javamelody/issue-6/comment-10/javamelody jboss 4.0.5 ok.PNG)

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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

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

Original comment by binarymo...@gmail.com on 24 Feb 2010 at 7:44

[GoogleCodeExporter]

ok, thanks for the information

Original comment by evernat@free.fr on 24 Feb 2010 at 9:02