Question
HCL
AU
Last activity: 4 May 2017 22:56 EDT
Issues with connecting to Websphere MQ from Pega using MDB listener
Hi ,
We are trying to connect to Websphere MQ from Pega through an MDB listener and facing the issues.
Stack Details:
Pega Version:7.2.1;
App Server:JBoss EAP 6.4.2.GA
Below are the details of a couple of approaches we tried.
Approach 1:
Configuring the Destination details in a separate xml file as described in the below pdn article:
https://pdn.pega.com/support-articles/jboss-512-websphere-mq-mdb-listener
The deployment of -ds.xml file is getting failed with parse exceptions caused by "conneciton-factories" tag.
Below are the errors:
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]
Hi ,
We are trying to connect to Websphere MQ from Pega through an MDB listener and facing the issues.
Stack Details:
Pega Version:7.2.1;
App Server:JBoss EAP 6.4.2.GA
Below are the details of a couple of approaches we tried.
Approach 1:
Configuring the Destination details in a separate xml file as described in the below pdn article:
https://pdn.pega.com/support-articles/jboss-512-websphere-mq-mdb-listener
The deployment of -ds.xml file is getting failed with parse exceptions caused by "conneciton-factories" tag.
Below are the errors:
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
Approach 2:
Create the connection pools and proxy objects destination objects by adding the appropriate tags in standalone.xml
- Configured the connection pools with NoTransaction and XATransaction as mentioned in the below article
- Configured the jndi name of the MQProxy object in the MDBListener rule form.
- Generate the MDB and updated prbeans jar with generated xml files
- Updated the ear file with the updated prbeans.jar and redeployed.
Found the following errors in the server logs :
.StartException in service jboss.deployment.subunit."prpc_j2ee14_jboss61JBM.ear"."prbeans.jar".component.NPPMDBListener.START: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceAdapterInternalException: MQJCA1011: Failed to allocate a JMS connection., error code: MQJCA1011 An internal error caused an attempt to allocate a connection to fail. See the linked exception for details of the failure.
at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee.jar:7.5.2.Final-redhat-2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_51]
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]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.RuntimeException: com.ibm.mq.connector.DetailedResourceAdapterInternalException: MQJCA1011: Failed to allocate a JMS connection., error code: MQJCA1011 An internal error caused an attempt to allocate a connection to fail. See the linked exception for details of the failure.
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:206)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:178)
at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee.jar:7.5.2.Final-redhat-2]
... 6 more
Caused by: com.ibm.mq.connector.DetailedResourceAdapterInternalException: MQJCA1011: Failed to allocate a JMS connection., error code: MQJCA1011 An internal error caused an attempt to allocate a connection to fail. See the linked exception for details of the failure.
at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:134)
at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:105)
at com.ibm.mq.connector.inbound.ConnectionHandler.allocateConnection(ConnectionHandler.java:310)
at com.ibm.mq.connector.inbound.MessageEndpointDeployment.acquireConnection(MessageEndpointDeployment.java:281)
at com.ibm.mq.connector.inbound.MessageEndpointDeployment.<init>(MessageEndpointDeployment.java:233)
at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:393)
at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:191)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:204)
... 8 more
Caused by: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0018: Failed to connect to queue manager '' with connection mode 'Client' and host name 'localhost(1414)'.
Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information.
at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:479)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:221)
at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:428)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6892)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6270)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:284)
at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6215)
at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:6271)
at com.ibm.mq.connector.inbound.ConnectionHandler.allocateConnection(ConnectionHandler.java:215)
... 13 more
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:209)
... 20 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2538;AMQ9204: Connection to host 'localhost(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2538;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.ConnectException[Connection refused],3=connnectUsingLocalAddress,4=TCP,5=Socket.connect]],3=localhost(1414),5=RemoteTCPConnection.connnectUsingLocalAddress]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2062)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)
at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:348)
... 19 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2538;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.ConnectException[Connection refused],3=connnectUsingLocalAddress,4=TCP,5=Socket.connect]
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.connnectUsingLocalAddress(RemoteTCPConnection.java:857)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1298)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:724)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:400)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:299)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:164)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1599)
... 21 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.8.0_51]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [rt.jar:1.8.0_51]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [rt.jar:1.8.0_51]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [rt.jar:1.8.0_51]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.8.0_51]
at java.net.Socket.connect(Socket.java:589) [rt.jar:1.8.0_51]
at java.net.Socket.connect(Socket.java:538) [rt.jar:1.8.0_51]
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$5.run(RemoteTCPConnection.java:842)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$5.run(RemoteTCPConnection.java:836)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_51]
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.connnectUsingLocalAddress(RemoteTCPConnection.java:834)
... 27 more
16:47:01,641 INFO [org.apache.struts2.config.AbstractBeanSelectionProvider] (ServerService Thread Pool -- 69) Choosing bean (struts) for (com
Could any one please guide the right approach in connecting from Pega to Websphere MQ through an MDB listener.
Regards
Paramesh
***Moderator Edit: Vidyaranjan | Updated Categories***
Pegasystems Inc.
US
You should follow this article to start with: https://docs-previous.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7. There are some details you need to pay attention:
You should follow this article to start with: https://docs-previous.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7. There are some details you need to pay attention:
In order to use MQ resource adapter, you will need to modify your jboss-ejb3.xml as follows (the default mdb resource adapter is hotnetq-ra, which is used by Pega PRAsync MDB for agent processing):
Edit the jboss-ejb3.xml to include the following segment under the <assembly-descriptor> element:
<mdb:resource-adapter-binding>
<ejb-name>your ejb name</ejb-name>
<mdb:resource-adapter-name>replace with the actual resource adapter name (i.e., wmq.jmsra.rar)</mdb:resource-adapter-name>
</mdb:resource-adapter-binding>
In addition, you need to add the following attribute to the <jboss:ejb-jar> element:
xmlns:mdb="urn:resource-adapter-binding"
HCL
AU
Hi Kelvin,
Thanks for your response.We have followed the steps that you mentioned. For some reason the MQ ProxConnection admin objects exposed as jndji object are not visible.Hence the Pega ear deployment is failing.We are able to deploy the ear if we pass the MQ properties through the ejb-jar xml as activation config properites,in this approach the deployment is successful and the onMessage of MessageDrivenBean is getting triggered as well when a message is received by the queue, but the listener activity is not triggered as the onMessage is failed with the following exception:
Hi Kelvin,
Thanks for your response.We have followed the steps that you mentioned. For some reason the MQ ProxConnection admin objects exposed as jndji object are not visible.Hence the Pega ear deployment is failing.We are able to deploy the ear if we pass the MQ properties through the ejb-jar xml as activation config properites,in this approach the deployment is successful and the onMessage of MessageDrivenBean is getting triggered as well when a message is received by the queue, but the listener activity is not triggered as the onMessage is failed with the following exception:
8:14:46,098 INFO [stdout] (Dispatcher-Thread-120) com.pega.pegarules.pub.PRException: Expecting a StreamMessage, received a message of type: com.ibm.jms.JMSMessage
18:14:48,028 INFO [stdout] (Dispatcher-Thread-120) From: (unknown)
18:14:48,034 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.readRequestData(JMSListener.java:1871)
18:14:48,048 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.handleRequest(JMSListener.java:1259)
18:14:48,062 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runOnce(JMSListener.java:709)
18:14:48,074 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.integration.engine.internal.services.jms.JMSListenerServant.invoke(JMSListenerServant.java:112)
18:14:48,088 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:327)
18:14:48,102 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:270)
18:14:48,115 INFO [stdout] (Dispatcher-Thread-120) at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
Below is the MDB defintion in the ejb-jar.xml:
<message-driven id="MessageDriven_NPPMDBListener">
<description>Message Driven Bean for JMS Listener NPPMDBListener</description>
<ejb-name>NPPMDBListener</ejb-name>
<ejb-class>com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>
destinationType
</activation-config-property-name>
<activation-config-property-value>
javax.jms.Queue
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
destination
</activation-config-property-name>
<activation-config-property-value>
QueueName
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
useJNDI
</activation-config-property-name>
<activation-config-property-value>
false
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
channel
</activation-config-property-name>
<activation-config-property-value>
ChannelName
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
hostName
</activation-config-property-name>
<activation-config-property-value>
IPAddress of the host
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
queueManager
</activation-config-property-name>
<activation-config-property-value>
NPAT01
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
port
</activation-config-property-name>
<activation-config-property-value>
1417
</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>
transportType
</activation-config-property-name>
<activation-config-property-value>
CLIENT
</activation-config-property-value>
</activation-config-property>
</activation-config>
<env-entry>
<env-entry-name>PRListener</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>NPPMDBListener</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>UseCMT</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<ejb-local-ref id="EJBLocalRef_NPPMDBListener_EngineBMTLocal">
<description/>
<ejb-ref-name>ejb/EngineBMTLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.pega.pegarules.internal.etier.interfaces.EngineLocalHome</local-home>
<local>com.pega.pegarules.internal.etier.interfaces.EngineLocal</local>
<ejb-link>EngineBMT</ejb-link>
</ejb-local-ref>
<ejb-local-ref id="EJBLocalRef_NPPMDBListener_EngineCMTLocal">
<description/>
<ejb-ref-name>ejb/EngineCMTLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.pega.pegarules.internal.etier.interfaces.EngineLocalHome</local-home>
<local>com.pega.pegarules.internal.etier.interfaces.EngineLocal</local>
<ejb-link>EngineCMT</ejb-link>
</ejb-local-ref>
</message-driven>
Happy to share more details that are required for better understanding of the issue.
Regards
Paramesh
Pegasystems Inc.
US
This simply means the message type on the queue is not matching what is expected in the Service-JMS request type. Notice that we only support JMS compliant message types: see this link for details: https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm