Hi,
The standalone client works fine until I import the standalone code as a
utility jar into a application running on Sun Application Server 8.2.
I run into NoClassDefFound Exception again:
Caused by: java.lang.NoClassDefFoundError
at
Based on JBM 1.4 documentation, the jar needed for remote client is:
jboss-aop.jar
jboss-remoting.jar
jbossall-client.jar
jboss-messaging-client.jar
jboss-mdr.jar - I had to add this one to get the signature class
javassist.jar
trove.jar
Try adding client/log4j.jar and see if that helps.
If that does not work, add -verbose:class to the JVM options on your client's
command line and run it again. This option prints out the JAR file location for
each class loaded; perhaps that will give use some clue as to the problem.
Also, post
My guess is the user has a mix and match of different versions on client and
server side.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224386#4224386
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4224386
Peter,
Adding log4j.jar causes exception in the ConnectionFactory lookup which is
before where the other exception happens.
Exception in thread main java.lang.NoSuchFieldError: TRACE
at
org.jboss.logging.Log4jLoggerPlugin.isTraceEnabled(Log4jLoggerPlugin.java:85)
I removed the
You should be using jboss_home/client/log4j.jar. Looks like you are using an
older version of log4j, before they added in trace level support.
I am suspecting the the log4j.jar file bacause TimerUtil imports a class from
there, and the error text is Could not initialize. This implies, to me, a
Thanks Peter for the quick response.
The log4j is from the client folder and it is apache version 1.2.14. Based on
the following post, it should resolve the issue.
http://lists.jboss.org/pipermail/jboss-user/2008-February/108795.html
However, if I don't include log4j.jar, I do not get
I moved my messaging app over to EAP 4.3, and there is what I had to add to my
client's classpath (beyond the JAR files for my app):
jboss-eap-4.3\jboss-as\client\jbossall-client.jar
jboss-eap-4.3\jboss-as\server\default\deploy\jboss-aop-jdk50.deployer\jboss-aop-jdk50.jar
Please discard my last post. What was in the classpath was the old log4j.jar
and the exception went away after I fixed the issue.
Peter you were right on, the TimerUtil class failed to initialize due to the
log4j.jar. Thanks!
View the original post :
JBM 1.4 doesn't have any special class loading to work with AOP,
jboss-remoting.jar etc. Take a look at the examples that comes with jbm 1.4.
The correct classpath can be found in the build.xml files.
View the original post :
10 matches
Mail list logo
