You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2022/12/07 17:34:00 UTC
[jira] [Updated] (ARTEMIS-4111) Session.recover () call ActiveMQServerMessagePlugin.messageAcknowledged (NORMAL)
[ https://issues.apache.org/jira/browse/ARTEMIS-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-4111:
------------------------------------
Fix Version/s: (was: 2.19.1)
(was: 2.23.1)
(was: 2.27.1)
> Session.recover () call ActiveMQServerMessagePlugin.messageAcknowledged (NORMAL)
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-4111
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4111
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMS, Tests
> Affects Versions: 2.12.0, 2.13.0, 2.14.0, 2.15.0, 2.16.0, 2.17.0, 2.18.0, 2.19.0, 2.19.1, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.23.1, 2.24.0, 2.25.0, 2.26.0, 2.27.0, 2.27.1
> Reporter: Andrey Yesenkov
> Priority: Major
> Fix For: 2.28.0
>
>
>
> {{When calling javax.jms.Session.recover () with ActiveMQJMSConstants.INDIVIDUAL_ACKNOWLEDGE, unacknowledged messages must be returned to the queue, that is, ClientSession.rollback (false) must be called from }}{{{}Session.recover (){}}}{{{}. In existing AMQ Artemis JMS versions If you call ClientSession.rollback (true), the ActiveMQServerMessagePlugin.messageAcknowledged () is called. Which is illogical and misleading.{}}}
> {{Tests are also needed to tests the }}{{Session.recover ()}}{{ of the call with parameters }}{{{}INDIVIDUAL_ACKNOWLEDGE{}}}{{{}{}}}{{ and the operation of the plugin.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)