You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/05/24 15:09:00 UTC

[jira] [Resolved] (ARTEMIS-3311) potential loss of error propagation to producer on failed paged message add

     [ https://issues.apache.org/jira/browse/ARTEMIS-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved ARTEMIS-3311.
---------------------------------
    Resolution: Fixed

> 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: 50m
>  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)