Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQException: MQJE001: Completion Code '2', Reason '2033' #158

Open
tsoft-globalproject opened this issue Sep 11, 2020 · 4 comments
Open

Comments

@tsoft-globalproject
Copy link

Hello,

These error codes appear when I start the client.
Could you help me understand why they are due?

2020-09-11 12:49:18.617 INFO - Successfully parsed configuration file!
2020-09-11 12:49:49.378 ERROR - Failed!
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
at com.ibm.mq.MQDestination.getInt(MQDestination.java:707) ~[com.ibm.mq.allclient-9.1.2.0.jar:9.1.2.0 - p912-L190308]
at com.ibm.mq.MQDestination.get(MQDestination.java:452) ~[com.ibm.mq.allclient-9.1.2.0.jar:9.1.2.0 - p912-L190308]
at ru.cinimex.exporter.ExporterLauncher.getAllPublishedMetrics(ExporterLauncher.java:83) [mq_exporter.jar:?]
at ru.cinimex.exporter.ExporterLauncher.main(ExporterLauncher.java:49) [mq_exporter.jar:?]

2020-09-11 12:50:08.036 ERROR - Connection with queue manager was closed:
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '6124'.
at com.ibm.mq.pcf.PCFMessageAgent.send(PCFMessageAgent.java:210) ~[com.ibm.mq.allclient-9.1.2.0.jar:9.1.2.0 - p912-L190308]
at ru.cinimex.exporter.mq.MQPCFSubscriber.run(MQPCFSubscriber.java:142) [mq_exporter.jar:?]

Thank you very much and greetings

@tsoft-globalproject
Copy link
Author

2020-09-11 12:50:08.181 ERROR - Error occurred during sending PCF command:
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '6124'.
at com.ibm.mq.pcf.PCFMessageAgent.send(PCFMessageAgent.java:210) ~[com.ibm.mq.allclient-9.1.2.0.jar:9.1.2.0 - p912-L190308]
at ru.cinimex.exporter.mq.MQPCFSubscriber.updateWithDirectPCFCommand(MQPCFSubscriber.java:104) [mq_exporter.jar:?]
at ru.cinimex.exporter.mq.MQPCFSubscriber.updateMetricsWithWildcards(MQPCFSubscriber.java:92) [mq_exporter.jar:?]
at ru.cinimex.exporter.mq.MQPCFSubscriber.run(MQPCFSubscriber.java:144) [mq_exporter.jar:?]
2020-09-11 12:50:20.135 INFO - Goodbye!

@tsoft-globalproject
Copy link
Author

According to the IBM website, the problem could be related to:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q041040_.htm

Explanation
An MQGET call was issued, but there is no message on the queue satisfying the selection criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval specified by the WaitInterval

This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is similar to MQGET. For the mqExecute call, the completion code can be either MQCC_WARNING or MQCC_FAILED:
If the completion code is MQCC_WARNING, some response messages were received during the specified wait interval, but not all. The response bag contains system-generated nested bags for the messages that were received.
If the completion code is MQCC_FAILED, no response messages were received during the specified wait interval.
Completion Code
MQCC_WARNING or MQCC_FAILED

Programmer response
If this is an expected condition, no corrective action is required.

If this is an unexpected condition, check that:
The message was put on the queue successfully.
The unit of work (if any) used for the MQPUT or MQPUT1 call was committed successfully.
The options controlling the selection criteria are specified correctly. All of the following can affect the eligibility of a message for return on the MQGET call:
MQGMO_LOGICAL_ORDER
MQGMO_ALL_MSGS_AVAILABLE
MQGMO_ALL_SEGMENTS_AVAILABLE
MQGMO_COMPLETE_MSG
MQMO_MATCH_MSG_ID
MQMO_MATCH_CORREL_ID
MQMO_MATCH_GROUP_ID
MQMO_MATCH_MSG_SEQ_NUMBER
MQMO_MATCH_OFFSET
Value of MsgId field in MQMD
Value of CorrelId field in MQMD
Consider waiting longer for the message.

@tsoft-globalproject
Copy link
Author

Hello,

Will it be necessary to adjust any parameter in the development of mq_exporter?

Please your comments.

Thank you.

@echerniak
Copy link
Contributor

Hello,
It seems like connection to MQ was broken during exporter processing. We have an issue #137 about reconnecting to queue manager. At the moment the most correct way of using mq exporter is running it as MQ service. Check more info here,

Best regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants