Il 08/01/2019 18:20, Gordon Sim ha scritto:
On 08/01/19 17:10, Alessandro Crotti - SMC Consulting wrote:
I have more sessions/consumers, for this reason I have more parallel
consumers which consume these messages.
Ok, then I think you need server side support for message grouping of
some kind.
What do you mean with your sentence: ...neither accept nor reject "E1
- S3", but hold on to it until you receive "E1 - S2"...
How can I hold on the message?
If in JMS you set client ack mode then don't call acknowledge until
you have received all the messages in sequence that you need.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
I'm in client ack mode. But if I do not call acknowledge for a message,
I must "stop" the thread until another consumer receives the right
message. With the consumer that is waiting I can't consume further
messages.
Moreover on Azure there is a "peek lock" and when it expires, the broker
considers the message "lost" and so available for another consuming attempt.
I will check better if grouping is supported by Azure and how it works.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
