[
https://issues.apache.org/jira/browse/ARTEMIS-3240?focusedWorklogId=581787&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-581787
]
ASF GitHub Bot logged work on ARTEMIS-3240:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Apr/21 13:54
Start Date: 13/Apr/21 13:54
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3541:
URL: https://github.com/apache/activemq-artemis/pull/3541#issuecomment-818754594
@clebertsuconic I was surprised that the scanreferences removed the messages
as part of the ack, but it looks like this is expected as rollback puts them
back. I added some logic to put them back via the failure handler, such that
the transaction rollback has work to do. The test captures the use case, an ack
in play before an server connection dies with a socket closed exception.
--
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: 581787)
Time Spent: 20m (was: 10m)
> Openwire nonBlockingRedelivery to true doesn't rollback the messages if the
> consumer is killed mid processing.
> --------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3240
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3240
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A message can be left in limbo of the ack is received before a failure of the
> connection. the ref has been removed from the consumer delivered list and
> rollback has no work to do. The normal openwire rollback processing that
> repopulates that list is missing in the failure case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)