[
https://issues.apache.org/jira/browse/AMQ-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3961.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Updated the TestClient test app to a JUnit based test case and applied the fix,
good catch.
> Durable subscriber only receives part of the persisted messages on re-connect
> -----------------------------------------------------------------------------
>
> Key: AMQ-3961
> URL: https://issues.apache.org/jira/browse/AMQ-3961
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.6.0
> Environment: Default configuraton of ActiveMQ under Linux or Windows
> Reporter: Andreas Mattes
> Assignee: Timothy Bish
> Fix For: 5.7.0
>
> Attachments: PrefetchSubscription.patch,
> PrefetchSubscriptionTest.java, TestClient.java
>
>
> A durable subscriber is connected to ActiveMQ using the ConnectionConsumer
> protocol, transacted sessions, and at most 1 message per session. While the
> subscriber is disconnected, the publisher publishes e.g. 10 messages. When
> the subscriber re-connects, it only receives 2 messages of those. If it
> repeatedly disconnects and re-connects, it receives 2 messages each time
> until all messages are received.
> Further investigation reveals that the problem lies in class
> org.apache.activemq.broker.region.PrefetchSubscription which does not
> re-check for further pending messages to be dispatched when committed message
> are removed from the list of dispatched but not yet acknowledged messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
