Application failing after updating to JBoss EAP 8 / Application Migration / Jakarta EE namespace

Solution Verified - Updated -

Issue

  • Application failing after updating to JBoss EAP 8 / Application Migration / Jakarta EE namespace
  • Application moved from EAP 7.4 to EAP 8.0 is failing with NoClassDefFoundError
java.lang.NoClassDefFoundError: Failed to link com/redhat/examples/Example (Module "deployment.example.war" from Service Module Loader): javax/servlet/http/HttpServlet
  • IBM MQ rar failing to deploy in JBoss EAP 8.0
=> {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.ra.deployer.\"wmq.jmsra.9.0.0.6.rar\"" => "WFLYJCA0046: Failed to start RA deployment [wmq.jmsra.9.0.0.6.rar]
    Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: wmq.jmsra.9.0.0.6.rar
    Caused by: java.lang.NoClassDefFoundError: Failed to link com/ibm/mq/connector/ResourceAdapterImpl (Module \"deployment.wmq.jmsra.9.0.0.6.rar\" from Service Module Loader): javax/resource/spi/Resourc
eAdapter"}

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content