[
https://issues.apache.org/activemq/browse/AMQ-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63327#action_63327
]
jijun wang commented on AMQ-2985:
---------------------------------
I just tried on Nov 12th SNAPSHOT build. It now will receive the same message
more than once. For example, I have some durable message sent out every 20
minutes. A client may receive accumulated durable message 3-7 when it first
reconnects. Then the client disconnected. After more than 20 minutes, it
reconnected second time and received message 8. It then disconnected again.
After another 20 more minutes, it reconnected the third time, but this time, it
received message 3-9. So message 3-8 were delivered with duplicate.
I have the following configuration for AMQ broker:
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="false"
memoryLimit="1mb">
<pendingSubscriberPolicy>
<fileCursor />
</pendingSubscriberPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="false"
memoryLimit="1mb">
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
...
<systemUsage>
<systemUsage sendFailIfNoSpaceAfterTimeout="3000">
<memoryUsage>
<memoryUsage limit="20 mb"/>
</memoryUsage>
</systemUsage>
</systemUsage>
> Missing messages in durable subscription with selector and KahaDB
> -----------------------------------------------------------------
>
> Key: AMQ-2985
> URL: https://issues.apache.org/activemq/browse/AMQ-2985
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
>
> With a selector and reconnecting durable sub, some messages appear missing as
> if they were acked in error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
