ClassFormatError using jboss-as-ejb-client-bom and jboss-as-jms-client-bom in standalone remote client in JBoss EAP 6

Solution Verified - Updated -

Issue

  • We are running into an issue when trying to remotely connect to a war application deployed in JBoss EAP 6. When we actually try using a method after the ejb lookup, we are seeing the following error. This error came up as one of our build and run requirements is to only use jars obtained from a maven repository. The client application was working fine with jboss-client.jar in the classpath. As recommended in the README.txt in the bin/client folder, we switched to jboss-as-ejb-client-bom and jboss-as-jms-client-bom, thus breaking our client application. Is the jboss-client.jar required for Java SE clients but the jars in the jboss-as-ejb-client-bom and jboss-as-jms-client-bom are needed for a "server client"?
java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/jms/JMSException
...

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6.0 - Beta

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.