[ 
https://issues.apache.org/jira/browse/ARTEMIS-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350480#comment-17350480
 ] 

ASF subversion and git services commented on ARTEMIS-3311:
----------------------------------------------------------

Commit 72c9cae8e1e2b8b4cf5909829edb31a33256cd6d in activemq-artemis's branch 
refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=72c9cae ]

ARTEMIS-3311 - ensure visibility of error state on operation context callback 
registration, fix and test


> potential loss of error propagation to producer on failed paged message add
> ---------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3311
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3311
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.17.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.18.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The operation context is tracking the pending io and registering completion 
> handlers. The default page file timed sync can happen before the response 
> handler callback registration, flag an error, but that error may not be 
> visible to the calling thread. The response hander will not always get an 
> error in this case.
> the issue is visibility of the errorCode flag in operation context, it needs 
> to be checked in a synchronisation block to match how it is being set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to