Apparently this is already logged at JIRA:
https://jira.jboss.org/jira/browse/JBMESSAGING-1616
Is there a workaround for this issue?
Thank you
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243509#4243509
Reply to the post :
can you make sure that the jbm-core.jar is the first thing in your classpath
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243525#4243525
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243525
Andy,
That was the first thing I tried after I read the Jira entry. jbm-core.jar is
at top of Eclipse project classpath. Unfortunately the issue remains.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243542#4243542
Reply to the post :
Gunther-
Can you create a self contained program which replicates this issue, file a
JIRA and attach it?
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243546#4243546
Reply to the post :
Tim
While creating and executing the test client from the command line everything
worked fine. After pointing the Eclipse Run configuration to the same JDK used
in CLI mode it also worked in eclipse. In Eclipse I was using IBM JDK 1.5.
thank you all for your efforts.
View the original post :
