[ 
https://issues.apache.org/jira/browse/AMQ-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994645#comment-15994645
 ] 

ASF subversion and git services commented on AMQ-6667:
------------------------------------------------------

Commit a0ba0bf4c6beaf50ce5e021ef5e4d493119bb1ef in activemq's branch 
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a0ba0bf ]

[AMQ-6667] gate cursor cache enablement on a single pending send and tidy up 
setbatch to always check outstanding async future list. Fix and test


> Many instances of "duplicate message ... from cursor" redirecting to dlq
> ------------------------------------------------------------------------
>
>                 Key: AMQ-6667
>                 URL: https://issues.apache.org/jira/browse/AMQ-6667
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.0
>
>
> In a high throughput scenario on a single destination there can be many 
> warnings of this kind:
> {code}
> [2017-03-21 09:51:37,548] WARN ActiveMQ BrokerService[localhost] Task-5 Queue 
> - queue://TEST, subscriptions=10, memory=102%, size=399, 
> pending=0, duplicate message ActiveMQTextMessage {commandId = 72, 
> responseRequired = true, 
> messageId = ID:Mac.fritz.box-64479-1490086286066-183:1:1:1:68, 
> originalDestination = null, originalTransactionId = null, 
> producerId = ID:Mac.fritz.box-64479-1490086286066-183:1:1:1, destination = 
> queue://TEST, transactionId = null, expiration = 0, 
> timestamp = 1490086297427, arrival = 0, brokerInTime = 1490086297427, 
> brokerOutTime = 1490086297427, correlationId = null, replyTo = null, 
> persistent = true, 
> type = null, priority = 4, groupID = null, groupSequence = 0, 
> targetConsumerId = null, compressed = false, userID = null, 
> content = org.apache.activemq.util.ByteSequence@8672edc, marshalledProperties 
> = null, dataStructure = null, redeliveryCounter = 0, size = 50216, properties 
> = null, 
> readOnlyProperties = false, readOnlyBody = false, droppable = false, 
> jmsXGroupFirstForConsumer = false, text = ...XXXXXXXXXXXX} 
> from cursor, is cursor audit disabled or too constrained? Redirecting to dlq
> {code}
> The broker loads messages twice into the cursor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to