activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: dlqDeliveryFailureCause : java.lang.Throwable: duplicate from store for queue
Date Wed, 11 Feb 2015 12:15:46 GMT
those warnings and the moving of message to the DLQ in 5.9 reflect
changes in the broker core that attempt to address duplicate dispatch
and skipped dispatch of messages when the cache and the message store
get out of sync.
In the main it can be avoided by disabling the cache but the best
approach would be to move to 5.11.0
The store/cursor interface was reworked to ensure order with the
cursor and to avoid the store providing duplicates.
There is mucho detail in
https://issues.apache.org/jira/browse/AMQ-4485 and
https://issues.apache.org/jira/browse/AMQ-5266

On 10 February 2015 at 16:33, Tecno Brain <cerebrotecnologico@gmail.com> wrote:
> Hi,
>
>   I'm using ActiveMQ 5.9.1
>
>   Recently I started to get a lot of messages into the DLQ. Nevertheless,
> from the logs, these messages are being sent into the DLQ by the producer,
> not the consumer.
>
> The messages in the DLQ have an additional attribute:
>     dlqDeliveryFailureCause
> with the value:
>     java.lang.Throwable: duplicate from store for queue:
> production@engineMessage
>
> The activemq.log shows a lot of warnings similar to the following segment:
>
> 2015-02-09 02:16:47,137 | WARN  |
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch@4d0a81a5
> :production@engineMessage,batchResetNeeded=false,storeHasMessages=true,size=1,cacheEnabled=true,maxBatchSize:2,hasSpace:true
> - cursor got duplicate:
> ID:ip-10-30-0-40.ec2.internal-52702-1422915270418-1:1:3:1:39357, 4 |
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ
> BrokerService[activemq-aws-prod] Task-39710
>
> 2015-02-09 02:16:47,137 | WARN  | duplicate message from store
> ID:ip-10-30-0-40.ec2.internal-52702-1422915270418-1:1:3:1:39357,
> redirecting for dlq processing | org.apache.activemq.broker.region.Queue |
> ActiveMQ BrokerService[activemq-aws-prod] Task-39710
>
>  Any idea what could be the cause? We had changes in our system but these
> don't seem to affect how we add messages into the queue.
>  Any pointers are appreciated.
>
> -Jorge

Mime
View raw message