[
https://issues.apache.org/jira/browse/AMQCPP-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591878#comment-13591878
]
Timothy Bish commented on AMQCPP-468:
-------------------------------------
The way the JMS API docs are written on this can be a bit misleading. When it
says that delivery is stopped and restarted it only means that in the sense
that for an active consumer the Message delivery is temporarily paused and the
unacknowledged messages are rolled back, and then delivery will resume again.
If however you've stopped the Session or Connection then delivery is stopped at
a higher level so called recover will roll back the Messages but delivery won't
start again until you actually call start() again.
> Session recover() does not seem to restart message delivery
> -----------------------------------------------------------
>
> Key: AMQCPP-468
> URL: https://issues.apache.org/jira/browse/AMQCPP-468
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.5.0
> Reporter: Martin Lichtin
> Assignee: Timothy Bish
> Attachments: amqcpp-468.cpp
>
>
> Session recover() method (implemented in AMQCPP-383) does not seem to restart
> message delivery.
> Will attach some test code.
> It runs a consumer that keeps received messages pending (does not ack them).
> I expected that after a Session recover(), the messages would be redelivered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
