Posted: Tue Nov 19, 2013 6:26 pm Post subject: Is there a way to set the priority on one MQ Input
Apprentice
Joined: 10 Jul 2013 Posts: 47
I have an app with two MQ Input nodes. One is the outside world interface for new requests, the other is for returning messages that are iterating through the processor.
When the Input queue for the former is full, and new messages come in to the re-entrant queue I want the re-entrant queue to get priority so those messages don't have to wait.
Yes, the famous flow with two MQ Input nodes again.
What seems to happen is that you run the flow with no additional instances and the outside world MQ Input reserves the thread for itself: it won't give the other MQ Input node a try until it has read it's own input queue empty.
This is exactly the reason why you can configure an MQ Input node to use an additional instances pool associated with the node itself instead of using the pool associated with the flow (which is shared).
If you make the re-entrance MQ Input use it's own pool, you are perhaps not exactly giving it a priority but at least making it "more equal", as the famous writing in the barn wall goes.
But then the flow will not run in one single thread any more and you really need to find a solution to your other problem.
Of course you can throw away the re-entrance MQ Input and put the re-entering messages in the same queue as the other messages - with higher priority.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum