Support Article
JMS configuration is different from the previous JBoss version
SA-10016
Summary
Using JBOSS EAP 6.x and setting up a JMS MDB listener to connect to an external message server yields the below error when starting the server.
Error Messages
SEVERE: PegaRULES Message Driven Bean has not acknowledged connection to JMS. Delaying for 30 seconds to wait for acknowledgement.
23:59:32,532 SEVERE [com.pega.pegarules.ra.priv] (Thread-97) PegaRULES Message Driven Bean has not acknowledged connection to JMS. Delaying for 30 seconds to wait for acknowledgement.
Steps to Reproduce
Set up a JMS MDB connector.
Root Cause
This is a question on how to setup an MDB using non default message broker (in this case - Tibco EMS).
Resolution
This issue is resolved through the following Local-change:
If the MDB listener is consuming messages from an external JMS message provider, such as IBM Websphere MQ, manually edit the jboss-ejb3.xml to include the following segment under the <assembly-descriptor> element:
<mdb:resource-adapter-binding>
<ejb-name>MDB name</ejb-name>
<mdb:resource-adapter-name>replace with the actual resource adapter name (i.e., 'wmq.jmsra.rar' for Websphere MQ resource adapter )</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
In addition, add the following attribute to the <jboss:ejb-jar> element:
xmlns:mdb="urn:resource-adapter-binding"
Published June 12, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.