[
https://issues.apache.org/jira/browse/AMQ-8464?focusedWorklogId=883113&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-883113
]
ASF GitHub Bot logged work on AMQ-8464:
---------------------------------------
Author: ASF GitHub Bot
Created on: 03/Oct/23 13:13
Start Date: 03/Oct/23 13:13
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1046:
URL: https://github.com/apache/activemq/pull/1046#issuecomment-1744954362
Overall my impressions are that this seems more complicated than it appears
to be at first glance because you need to properly handle rolling things back
and making sure that in certain modes the client acts like the receive was
never called. I am not sure that simply re-adding the message to the unconsumed
list is enough. There's a lot of code in rollback() to handle things like
duplicate detection so the message can be received again.
So that being said I think this needs more work and a lot more testing and
might need to wait for 6.1.0
Issue Time Tracking
-------------------
Worklog Id: (was: 883113)
Time Spent: 2h (was: 1h 50m)
> Implement JMS 2.0 Consumer receiveBody
> --------------------------------------
>
> Key: AMQ-8464
> URL: https://issues.apache.org/jira/browse/AMQ-8464
> Project: ActiveMQ
> Issue Type: Task
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 6.0.0, 5.18.3
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
