You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment you can offer one queue to the ibmmq trigger. I want to change the queueName parameter so that it accepts multiple queues (comma (,) separated). The code will have to be changed to request the current depth per queue and only use the current depth from the queue with the most messages.
Use-Case
Our applications work with a lot of queues. Whether the application needs to scale does not depend on 1 queue. I know it is possible to set multiple triggers, but in our case that will be a lot. Also, multiple connections are set up which is unnecessary.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
Although you can specify multiple queues, I leave the parameter name the same (queueName) so that everything continues to work properly. But queueNames is also supported.
The text was updated successfully, but these errors were encountered:
Proposal
At the moment you can offer one queue to the
ibmmq
trigger. I want to change thequeueName
parameter so that it accepts multiple queues (comma (,
) separated). The code will have to be changed to request the current depth per queue and only use the current depth from the queue with the most messages.Use-Case
Our applications work with a lot of queues. Whether the application needs to scale does not depend on 1 queue. I know it is possible to set multiple triggers, but in our case that will be a lot. Also, multiple connections are set up which is unnecessary.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
Although you can specify multiple queues, I leave the parameter name the same (
queueName
) so that everything continues to work properly. ButqueueNames
is also supported.The text was updated successfully, but these errors were encountered: