Question
CSAA
US
Last activity: 30 Apr 2021 14:50 EDT
Received MQ message Exception: MQJE001: Completion Code '2', Reason '2033'
Hi
I am having a Connect-MQ rule. While invoking the rule in live it is sometime giving exception. Please find the exception logs below.
Hi
I am having a Connect-MQ rule. While invoking the rule in live it is sometime giving exception. Please find the exception logs below.
Please help me to resolve this.
Thanks and Regards
Naveen Raja
Accepted Solution
Updated: 8 Jun 2020 12:47 EDT
Pegasystems Inc.
US
My thoughts:
1. The root cause can be many (e.g., latency, data issue, etc). Given it is sporadic, I hope you have a lower env to debug. Pega does not have any more details as the client is all IBM classes, check this link: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q131530_.htm. You can also check the MQ server log to see if there are any clues (attach if possible, we can review it here).
2. This likely requires review of your case flow logic and how MQ connector is used in your application flow, the invokeMQConnector activity throws these exceptions:
My thoughts:
1. The root cause can be many (e.g., latency, data issue, etc). Given it is sporadic, I hope you have a lower env to debug. Pega does not have any more details as the client is all IBM classes, check this link: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q131530_.htm. You can also check the MQ server log to see if there are any clues (attach if possible, we can review it here).
2. This likely requires review of your case flow logic and how MQ connector is used in your application flow, the invokeMQConnector activity throws these exceptions:
} catch (ActivityTerminateException ate) {
throw ate; // Terminate all activity processing
} catch (com.pega.pegarules.pub.PRAppRuntimeException arte) {
throw arte;
} catch (PRRuntimeException prre) {
if (!pz_methodStatusUpdated) {
pega.setThreadPropertyValue(".pxMethodStatus", prre.toString());
}
pega.activityStepExceptionHandler(prre, snapshotLocalVariables(),
pz_CurrentTraceInfo, pz_CurrentStepNum);
throw prre;
} catch (RuntimeException re) {
pega.setThreadPropertyValue(".pxMethodStatus", re.toString());
pega.activityStepExceptionHandler(re, snapshotLocalVariables(),
pz_CurrentTraceInfo, pz_CurrentStepNum);
throw re;
} finally {
pega.activityEpilog(snapshotLocalVariables(), pz_CurrentTraceInfo);
}
Pegasystems Inc.
US
Is this happening consistently or sporadically? What is your MQ server version? Here is the description of the MQ error code: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q041040_.htm
CSAA
US
Hi Kevin
This is happening sporadically. Whenever this exception is happening, the case is routed to the Pega 7.4 ootb NonConnection Error workbasket though all the necessary error handling has been handled.
After sometime if an operator is performing the case from the workbasket, it is success and getting through the flow. Below are the 2 points we need to solve.
1. What is the root cause of this issue(MQ Exception)
2. Even though all the error and exception scenarios are handled gracefully, why this runtime exception is not captured and the case is getting routed to Pega ootb non-connection error WB.
Thanks and Regards
Naveen Raja
Accepted Solution
Updated: 8 Jun 2020 12:47 EDT
Pegasystems Inc.
US
My thoughts:
1. The root cause can be many (e.g., latency, data issue, etc). Given it is sporadic, I hope you have a lower env to debug. Pega does not have any more details as the client is all IBM classes, check this link: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q131530_.htm. You can also check the MQ server log to see if there are any clues (attach if possible, we can review it here).
2. This likely requires review of your case flow logic and how MQ connector is used in your application flow, the invokeMQConnector activity throws these exceptions:
My thoughts:
1. The root cause can be many (e.g., latency, data issue, etc). Given it is sporadic, I hope you have a lower env to debug. Pega does not have any more details as the client is all IBM classes, check this link: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q131530_.htm. You can also check the MQ server log to see if there are any clues (attach if possible, we can review it here).
2. This likely requires review of your case flow logic and how MQ connector is used in your application flow, the invokeMQConnector activity throws these exceptions:
} catch (ActivityTerminateException ate) {
throw ate; // Terminate all activity processing
} catch (com.pega.pegarules.pub.PRAppRuntimeException arte) {
throw arte;
} catch (PRRuntimeException prre) {
if (!pz_methodStatusUpdated) {
pega.setThreadPropertyValue(".pxMethodStatus", prre.toString());
}
pega.activityStepExceptionHandler(prre, snapshotLocalVariables(),
pz_CurrentTraceInfo, pz_CurrentStepNum);
throw prre;
} catch (RuntimeException re) {
pega.setThreadPropertyValue(".pxMethodStatus", re.toString());
pega.activityStepExceptionHandler(re, snapshotLocalVariables(),
pz_CurrentTraceInfo, pz_CurrentStepNum);
throw re;
} finally {
pega.activityEpilog(snapshotLocalVariables(), pz_CurrentTraceInfo);
}
Verizon Wireless
US
@KevinZheng_GCS We are also using Connect-MQ, but getting failure to post the message in the IBM MQ. Below is the error message from MQ team. I am Only using Request method to post the message in Connect-MQ rule.
@KevinZheng_GCS We are also using Connect-MQ, but getting failure to post the message in the IBM MQ. Below is the error message from MQ team. I am Only using Request method to post the message in Connect-MQ rule.
ReasonCode: 2035 EventName: Not Authorized Type 2 - MQRC_NOT_AUTHORIZED (2035, X'7F3') EventType: Authority Description: On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the options specified. ReasonQualifier: 2 (MQRQ_OPEN_NOT_AUTHORIZED) OpenOptions: 17 MQOO_OUTPUT MQOO_INPUT_AS_Q_DEF ApplType: 6 (MQAT_UNIX) ApplName: catalina.startup.Bootstrap