JBossDeveloper

I have the same problem. Did you fix it some how?

/Søren

i finally fixed te problem cleaning all temp files from jboss(temp, and work->localhost)). I didn´t delete any finally, in fact when i deleted the file my webservices were not published.

Regards kike.

Log4j 1.2.14 has direct support for the trace logging level. Earlier versions of JBoss used older versions of log4j which did not support the trace level.

The NoSuchFieldError: TRACE that appears in the first post refers to class org.apache.log4j.Level. It evidences the presence of an older log4j version in the classpath.

In my case I was getting this error in the client side. It turned out that my classpath contained an older version of log4j which was not compatible with the jboss 4.2 libraries. Upgrading log4j to version 1.2.14 did the trick for me. I mention it here in case these findings help someone.

"cornfield" wrote:
Hi,camunda
I tried your method, my application running fine! Thank you! But it's a camunda method,right? I don't know if there a official solution.

Hi,mithilwane & sashaxiv & sipcity
My app used jbossall-client.jar in client, so I delete "Log4jLoggerPlugin.class" in "jboss4.2.0GA/client/jbossall-client.jar". My app loggin fine! Do you use this jar? You can try it!

Thanks all repliers!!!

I experienced the same problem when I had log4j-1.2.8.jar in my classpath. When I replaced this with log4j-1.2.15.jar the problem went away.

I Did everything recommended by everyone and still got the same problem. I have no references to older versions of log4j throught my workspace. I have gone so far as to copy the version recommended into all the lib folders throughout jboss. I finally did the class delete thing and bam, it worked first try.