[
https://issues.apache.org/jira/browse/AMQ-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521648#comment-14521648
]
Gary Tully commented on AMQ-5752:
---------------------------------
I pushed a test that shows the nasty behaviour[1] the fix is not obvious
because it points to a short fall in how we deal with duplicate sends, the
store may or may not track them and the cursor may or may not be able to so at
the moment a send call will not fail on a duplicate send, it has to throw an
exception b/c there is currently no return state from queue.send but it will
take some thought to figure out where best to deal with this.
http://git-wip-us.apache.org/repos/asf/activemq/commit/82200b6e
> Move and copy message does not work in web console
> --------------------------------------------------
>
> Key: AMQ-5752
> URL: https://issues.apache.org/jira/browse/AMQ-5752
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.11.0, 5.11.1
> Reporter: Petter Nordlander
>
> When moving a message with web console (clicking message, select target queue
> and press move) the message get's lost.
> The following message is found in the ActiveMQ log. It's wierd since a move
> should not trigger a duplicate error since the message should be moved.
> ` INFO | Moving message
> FROM(ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1) to TO
> WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@42db79bc:TO,batchResetNeeded=false,size=0,cacheEnabled=true,maxBatchSize:1,hasSpace:true,pendingCachedIds.size:1,lastSyncCachedId:null,lastSyncCachedId-seq:null,lastAsyncCachedId:null,lastAsyncCachedId-seq:null,store=permits:9999,sd=nextSeq:3,lastRet:MessageOrderCursor:[def:0,
> low:0, high:0],pending:0 - cursor got duplicate send
> ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1 seq:
> org.apache.activemq.store.kahadb.KahaDBStore$StoreQueueTask$InnerFutureTask@38864035
> WARN | Duplicate message add attempt rejected. Destination: QUEUE://TO,
> Message id: ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1`
> The same problem goes for "copy". But, the original message does not get
> deleted. The error in the log is similar:
> `INFO | FROM(ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1)
> copy to TO
> WARN |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@42db79bc:TO,batchResetNeeded=false,size=0,cacheEnabled=true,maxBatchSize:1,hasSpace:true,pendingCachedIds.size:1,lastSyncCachedId:null,lastSyncCachedId-seq:null,lastAsyncCachedId:null,lastAsyncCachedId-seq:null,store=permits:9999,sd=nextSeq:1,lastRet:MessageOrderCursor:[def:0,
> low:0, high:0],pending:0 - cursor got duplicate send
> ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1 seq:
> org.apache.activemq.store.kahadb.KahaDBStore$StoreQueueTask$InnerFutureTask@571547ee
> WARN | Duplicate message add attempt rejected. Destination: QUEUE://TO,
> Message id: ID:petters-mbp.got.vgregion.se-65058-1430309626002-5:1:1:1:1`
> The problem with move is a bit critical since it can cause loss of important
> data.
> Verified in AMQ 5.11.0 and 5.11.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
