[
https://issues.apache.org/jira/browse/ARTEMIS-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867353#comment-17867353
]
ASF subversion and git services commented on ARTEMIS-4936:
----------------------------------------------------------
Commit 9a0797509d939cfd3b473a16e5b26b9119305443 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9a0797509d ]
ARTEMIS-4936 verify response correlationId when using Core client
If, for whatever reason, the response for a packet sent with blocking
semantics is never returned it's possible that an async response
received in the interventing time will be interpreted as the current
response. This is because ChannelImpl does not verify the correlation
ID set on the response packet when it is received.
> Verify response correlationId in Core client
> --------------------------------------------
>
> Key: ARTEMIS-4936
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4936
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
