This is just a problem with LOG4J class.
With version higher than 1.2.8, the TRACE field is added.
You probably forgot a reference to an older version of LOG4J.
check all your LOG4J references in your project.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=41031
I do not have CLASSPATH env variable set up,
I think this is something to do with the classloading
Yes you are correct, we got two options
1) delete the log4j from the other projects
2) update the jboss log4j with other projects
even though above works, It doent look nice, the best way is how
If you scan through the forums you will see that log4j issues with classloading
is a headache frequently encountered by users of JBoss AS. The best solution
appears to be to banish log4j.jar from any deployed apps.
By the way, I hope that you do not have the CLASSPATH env var set.
View the ori
Yes you are correct, old log4j file was in one of my applications, I had to
upgrade it to the new one, now I could get the application server up.
Isn't there a better way to achieve the log4j class loading in isolation
instead of impacting the other running applications.
Thanks
View the origin
It does appear that there is an older version of Log4J hanging around. Do two
things:
1) Post the results from entering: $JAVA_HOME/bin/java
2) Change the OPTS env var in run.conf, adding the option '-verbose:class'.
Then start the app server again, redirecting the output to a file (you will g
