-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Use MQCMD_INQUIRE_Q instead of queue.inquire #3997
Use MQCMD_INQUIRE_Q instead of queue.inquire #3997
Conversation
abb8c06
to
e55853b
Compare
e55853b
to
8a51945
Compare
Codecov Report
@@ Coverage Diff @@
## master #3997 +/- ##
==========================================
- Coverage 86.09% 84.66% -1.43%
==========================================
Files 763 10 -753
Lines 41367 450 -40917
Branches 5061 55 -5006
==========================================
- Hits 35613 381 -35232
+ Misses 4365 59 -4306
+ Partials 1389 10 -1379 |
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #3997 +/- ##
==========================================
- Coverage 86.09% 84.66% -1.43%
==========================================
Files 763 10 -753
Lines 41367 450 -40917
Branches 5061 55 -5006
==========================================
- Hits 35613 381 -35232
+ Misses 4365 59 -4306
+ Partials 1389 10 -1379 |
I don't understand what you mean there |
Previously, we call Now, calling |
What does this PR do?
Since we added support for local queues, when a local queue is assigned to a cluster, the method
queue.inquire
will raise this warning:WARNING: MQRC_SELECTOR_NOT_FOR_TYPE
But using
MQCMD_INQUIRE_Q
does not have this issue. That will also avoid calling the IBM MQ server only once instead of once per attribute we want to get.Motivation
Additional Notes
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached