[
https://issues.apache.org/jira/browse/ARTEMIS-3311?focusedWorklogId=601223&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-601223
]
ASF GitHub Bot logged work on ARTEMIS-3311:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/May/21 15:07
Start Date: 24/May/21 15:07
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3592:
URL: https://github.com/apache/activemq-artemis/pull/3592#issuecomment-847107856
yep. full tests look good.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 601223)
Time Spent: 40m (was: 0.5h)
> 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)
