[
https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-2140.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 5.4.0)
5.3.0
Assignee: Rob Davies
Set the prefetch to zero for the consumer - see
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
> Message expriation causes that receiver gets stuck
> --------------------------------------------------
>
> Key: AMQ-2140
> URL: https://issues.apache.org/activemq/browse/AMQ-2140
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: WinXP,
> Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
> Reporter: Juraj Kuruc
> Assignee: Rob Davies
> Priority: Critical
> Fix For: 5.3.0
>
> Attachments: ttl_amq_bug.zip
>
>
> Using TimeToLive on message producer set on value <> 0 causes that receiver
> stops to receive messages at specific circumstances (see test case
> descr.),until receiver is restarted.
> Steps to reproduce:
> - start RedeliveryConsumer (waits 1000ms to ack)
> - start DlqConsumer
> - start RedeliveryProducer (timeToLive=500ms)
> Result:
> - only first message is received and acknowledged by RedeliveryConsumer
> - after restart of RedeliveryConsumer another 9 are received by DlqConsumer
> Similar behaviour was observed if message expires between delivery and first
> redelivery (after first calling session recover) client stops to receive and
> messages aren't post even to DLQ.Any further sending has no effect on
> receiver.
> This behaviour is independent on destination type (queue/topic) or using of
> persistency. Using of message expiration therefore become unreliable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
