Support Article

Unable to connect to MQ through MDB listener

SA-37356

Summary



User tried to create an MDB listener with an MQ queue as a source by following the steps mentioned in the following URL:

https://pdn.pega.com/support-articles/jboss-512-websphere-mq-mdb-listener

Issue is that the Connection factory is not being shown in the MDB ruleform.


Error Messages



Errors while server start up:
org.jboss.msc.service.StartException in service jboss.deployment.unit."wmqueue-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "wmqueue-ds.xml"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server.jar:7.5.2.Final-redhat-2]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: IJ010061: Unexpected element: connection-factories
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:99)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server.jar:7.5.2.Final-redhat-2]
... 5 more
Caused by: org.jboss.jca.common.metadata.ParserException: IJ010061: Unexpected element: connection-factories
at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:128)
at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:89)
... 6 more

Errors after server started:

14:49:26,918 ERROR [stderr] (Thread-110) INFO: Publishing acknowledgement request message: {NodeID=01e6426ce5a1d251aff145b36303d91c, ClientID=01e6426ce5a1d251aff145b36303d91c, ResourceType=ACK_REQUIRED}
14:49:26,909 INFO [com.pega.pegarules.ra.priv] (Thread-110) Publishing acknowledgement request message: {NodeID=01e6426ce5a1d251aff145b36303d91c, ClientID=01e6426ce5a1d251aff145b36303d91c, ResourceType=ACK_REQUIRED}
14:49:31,947 ERROR [stderr] (Thread-110) Mar 21, 2017 2:49:31 PM com.pega.pegarules.ra.priv.PRResourceNode$AsyncTask run
14:49:31,956 ERROR [stderr] (Thread-110) SEVERE: PegaRULES Message Driven Bean has not acknowledged connection to JMS. Delaying for 30 seconds to wait for acknowledgement.
14:49:31,947 SEVERE [com.pega.pegarules.ra.priv] (Thread-110) PegaRULES Message Driven Bean has not acknowledged connection to JMS. Delaying for 30 seconds to wait for acknowledgement.
14:49:31,982 ERROR [stderr] (Thread-110) Mar 21, 2017 2:49:31 PM com.pega.pegarules.ra.priv.PRResourceNode$AsyncTask run
14:49:31,991 ERROR [stderr] (Thread-110) INFO: Publishing acknowledgement request message: {NodeID=01e6426ce5a1d251aff145b36303d91c, ClientID=01e6426ce5a1d251aff145b36303d91c, ResourceType=ACK_REQUIRED}
14:49:31,982 INFO [com.pega.pegarules.ra.priv] (Thread-110) Publishing acknowledgement request message: {NodeID=01e6426ce5a1d251aff145b36303d91c, ClientID=01e6426ce5a1d251aff145b36303d91c, ResourceType=ACK_REQUIRED}


Steps to Reproduce



https://pdn.pega.com/support-articles/jboss-512-websphere-mq-mdb-listener
  • Stack Details:
  • JBoss Version: JBoss EAP 6.4.2.GA
  • Pega Version:7.2.1


Root Cause



Issue with configuration or connection between JBOSS and MQ is suspected.

Resolution



Here’s the explanation for the reported behavior:

1) Link used as reference is specific to earlier version of PRPC and JBOSS:
https://pdn.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7
2) Above link must be used to deploy MDB listener.
3) Note that configuration must be completed to use correct resource adapter for MQ.
4) Since configuration does not works between third party MQ and JBOSS, analysis from third party must be requested.

Published May 2, 2017 - Updated May 16, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.