Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Unable to deploy JMS Message Listener on JBoss EAP 7.3.0.GA using IBM MQ Resource Adapter

    Posted on

    I am experiencing an issue deploying a JMS Message Listener on JBoss EAP 7.3.0.GA using the IBM MQ Resource Adapter. The error I receive when deploying the application is:

    java.lang.IllegalStateException: WFLYEJB0383: No message endpoint of type javax.jms.MessageListener was found in the resource adapter wmq.jmsra.rar

    Caused by: java.lang.IllegalStateException: WFLYEJB0383: No message listener of type javax.jms.MessageListener found in resource adapter wmq.jmsra-7.5.0.7.rar
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createActivationSpecs(MessageDrivenComponentCreateService.java:142)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:105)
    at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:86)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.start(MessageDrivenComponentCreateService.java:93)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)

    An extract of the relevant code snippet for my Message Driven Bean can be found in the attached Mdb.java file.

    An extract of the standalone.xml containing the relevant configuration part is attached as standalone.xml.

    The wmq.jmsra.rar file is properly deployed in the standalone/deployments directory, and its version is 9.2.0.8-p920-008-230110.

    The wmq.jmsra.rar deploys correctly when it is deployed by itself.

    The version of the IBM WebSphere MQ Resource Adapter I am using is 9.2.0.8-p920-008-230110.

    I have already tried several suggestions, including modifying the destination property value in the @ActivationConfigProperty annotation and ensuring that the resource adapter is correctly deployed. However, the issue persists.

    Any help or guidance on how to resolve this problem would be greatly appreciated.

    Attachments

    by

    points

    Responses

    Red Hat

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat, Inc.