I am guessing, you are using JBoss 4.2.x version of JBoss. If yes, then have a
look at http://www.jboss.com/index.html?module=bbop=viewtopicp=4050046#4050046
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120386#4120386
Reply to the post :
Well, I'm using JBoss 4.2.2... and I read that topic,
As I stated in the previous post, I've already referenced the log4j.jar in the
JBOSS_HOME/client, but the client still throws that exception.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120432#4120432
Just to make sure that this particular log4j.jar is being used and not some
other version of log4j jar from your classpath, add the -verbose:class JVM
parameter while running your client application. This will print out to STDOUT
the classes which are being loaded and the jar file from which
For more specific, I'm using JBoss 4.2.2, MyEclipse 5.5 to create my EJB
project, I created the client outside MyEclipse.
I create a TestClient again in MyEclipse, and another funny thing happened,
please have a look here:
http://www.jboss.com/index.html?module=bbop=viewtopicp=4120693#4120693
