Announcement Announcement Module
Collapse
No announcement yet.
TaskExecutor and acknowledgements? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • TaskExecutor and acknowledgements?

    Concurrent consumers is a little misleading because whilst this refers to concurrent processors of messages from the queue it doesn't necessarily mean consumers concurrently reading the queue. Now if I'm not mistaken if you have a Consumer keep a reference to it's session in a 1:1 mapping whenever you commit the session you're essentially only acknowledging all messages that have been processed by that Consumer since the last commit took place for that session? Is that right? What does this mean?

    "Specifying a TaskExecutor for listener execution affects acknowledgement semantics. Messages will then always get acknowledged before listener execution, with the underlying Session immediately reused for receiving the next message. Using this in combination with a transacted session or with client acknowledgement will lead to unspecified results!"

    ....
Working...
X