You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2009/01/29 17:42:59 UTC

[jira] Reopened: (AMQ-2087) Redelivery after rollback does not seem to work well

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

Gary Tully reopened AMQ-2087:
-----------------------------


going to bite the bullit on this and augment the close command (RemoveInfo) with a deliveredSequenceId so that the broker can determine which of the prefetched messages were actually delivered to the end consumer.
This will require some api changes in the destination which will break DestinationFilters but something has got to give. 

> Redelivery after rollback does not seem to work well 
> -----------------------------------------------------
>
>                 Key: AMQ-2087
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2087
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Guillaume Nodet
>            Assignee: Gary Tully
>             Fix For: 5.3.0
>
>         Attachments: AMQ-2087.test.diff
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.