Gary Tully commented on AMQ-6562:

The WARN is expected when the cache is exhausted and page in begins at the last 
ack location. Irrespective of the last cached message id in the cursor.
Any message that has not been acked will get replayed and the audit will trap 
it as a duplicate. However this scenario should not result in messaged going to 
the DLQ.
In addition there is a leak of message references b/c the duplicates detected 
are not resolved by the TopicStorePrefetch cursor.

> WARN TopicStorePrefetch cursor got duplicate from store
> -------------------------------------------------------
>                 Key: AMQ-6562
>                 URL: https://issues.apache.org/jira/browse/AMQ-6562
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Message Store
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.0
> Intermittent WARN in the log for durable topic subs:
> {code}17/01/13 10:45:35 WARN cursors.AbstractStoreCursor: 
> TopicStorePrefetch(CONNECTION-my_sub_1,my_sub_1,storeHasMessages=false) 
> ID:localhost-49595-1484304335002-6:1:1:1 - 
> org.apache.activemq.broker.region.cursors.TopicStorePrefetch@37e3cc57:T1,batchResetNeeded=false,size=14,cacheEnabled=false,maxBatchSize:200,hasSpace:true,pendingCachedIds.size:0,lastSyncCachedId:null,lastSyncCachedId-seq:null,lastAsyncCachedId:null,lastAsyncCachedId-seq:null
>  - cursor got duplicate from store ID:localhost-49595-1484304335002-4:1:1:1:1 
> seq: null
> {code}

This message was sent by Atlassian JIRA

Reply via email to