Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Consider a Core client sending packets with blocking semantics and a confirmationWindowSize >= 0. For example, consider such a client sending multiple durable messages in a transaction and then committing that transaction. If, for whatever reason, the response for the commit packet is never returned it's possible that the call to commit will still succeed. This is because ChannelImple does not verify the correlation ID set on the commit packet and will interpret a previous response as the current response to the commit.
Attachments
Issue Links
- is related to
-
ARTEMIS-3729 JMS CORE client session commit doesn't work after async sends
- Closed
- links to