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

Can we get the upper bound of the GET-ASYNC operation. #184

Open
sanohdar opened this issue Aug 23, 2024 · 1 comment
Open

Can we get the upper bound of the GET-ASYNC operation. #184

sanohdar opened this issue Aug 23, 2024 · 1 comment

Comments

@sanohdar
Copy link

sanohdar commented Aug 23, 2024

Please include the following information in your ticket.

  • mq-mqi-nodejs version(s) that are affected by this issue. (2.0.4)
  • A small code sample that demonstrates the issue.

Few queries related to Limitation of GET ASYNC operation

  1. What is the total no. of handlers available to simultaneously support get operation ?
  2. is there any FLAG by which we can control the connection polling here ?
  3. we need these limitation information for the documentation purpose.
@ibmmqmet
Copy link
Collaborator

There's no particular limits on number of consumers from a queue. The setTuningParameters function has a few documented controls on message consumption, but they're unlikely to need to be changed.

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