Support Article
Fails to read MQ response message with Pega 7.1.7
SA-29766
Summary
Invoke MQ connector activity throwing an exception while reading message from the queue.
Error Messages
2016-10-06 23:49:25,536 [ WebContainer : 23] [ STANDARD] [ ] [ternational:01.01.01] ( internal.mgmt.Executable) ERROR C7123078 - Exception
com.pega.pegarules.pub.services.ConnectorException: received MQ message of unrecognized type: 1
at com.pegarules.generated.activity.ra_action_invokemqconnector_cf24cf43e0c6ee600c8c201d4ac41c8c.step1_circum0(ra_action_invokemqconnector_cf24cf43e0c6ee600c8c201d4ac41c8c.java:1546)
at com.pegarules.generated.activity.ra_action_invokemqconnector_cf24cf43e0c6ee600c8c201d4ac41c8c.perform(ra_action_invokemqconnector_cf24cf43e0c6ee600c8c201d4ac41c8c.java:69)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10454)
at com.pegarules.generated.activity.ra_action_invoke_09ba3826238149ebe676e5e05b1da689.step4_circum0(ra_action_invoke_09ba3826238149ebe676e5e05b1da689.java:366)
at com.pegarules.generated.activity.ra_action_invoke_09ba3826238149ebe676e5e05b1da689.perform(ra_action_invoke_09ba3826238149ebe676e5e05b1da689.java:120)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pegarules.generated.activity.ra_action_docuploadinquireprocessing_5e951e8427bb9fc98184ea466ca4631f.step11_circum0(ra_action_docuploadinquireprocessing_5e951e8427bb9fc98184ea466ca4631f.java:542)
at com.pegarules.generated.activity.ra_action_docuploadinquireprocessing_5e951e8427bb9fc98184ea466ca4631f.perform(ra_action_docuploadinquireprocessing_5e951e8427bb9fc98184ea466ca4631f.java:170)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.runSimulationActivity(ServiceAPI.java:2566)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.processSimulation(ServiceAPI.java:2287)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.processServiceSimulation(ServiceSimulator.java:689)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.invokeServiceHTTP(ServiceSimulator.java:367)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.execute(ServiceSimulator.java:168)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.executeServiceSimulation(PRServiceUtils.java:1873)
at com.pegarules.generated.activity.ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.step7_circum0(ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.java:705)
at com.pegarules.generated.activity.ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.perform(ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.java:249)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10454)
at com.pegarules.generated.activity.ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.step12_circum0(ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.java:1296)
at com.pegarules.generated.activity.ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.perform(ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.java:289)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:641)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:435)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:3252)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:384)
at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
Steps to Reproduce
1. Keep response message with messageType as Request type value 1 in queue.
2. InvokeMQConnector activity to read message.
Root Cause
User is reading MQ message from the queue which is having invalid the message type in header causing the issue.
Resolution
Here’s the explanation for the reported behavior:
User is sending messageType as MQMT_REQUEST ( = 1) which is invalid as InvokeMQConnector is expecting MQMT_REPLY (=2) or MQMT_DATAGRAM (=8) or MQMT_REPORT (=4) to read the message from queue.
Issue resolves once the user had passed the message type value as MQMT_REPLY.
Published November 15, 2016 - 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.