You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Juraj Kuruc (JIRA)" <ji...@apache.org> on 2009/02/23 18:42:59 UTC
[jira] Created: (AMQ-2140) Message expriation causes that receiver
gets stuck
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:
« Hide
WinXP,
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Reporter: Juraj Kuruc
Priority: Critical
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.
[jira] Updated: (AMQ-2140) Message expriation causes that receiver
gets stuck
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2140:
----------------------------
Fix Version/s: 5.4.0
> 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
> Priority: Critical
> Fix For: 5.4.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.
[jira] Resolved: (AMQ-2140) Message expriation causes that receiver
gets stuck
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQ-2140) Message expriation causes that
receiver gets stuck
Posted by "Fabien Brousse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51801#action_51801 ]
Fabien Brousse commented on AMQ-2140:
-------------------------------------
Tested with 5.2.0, same behaviour.
> 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
> Priority: Critical
> 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.
[jira] Updated: (AMQ-2140) Message expriation causes that receiver
gets stuck
Posted by "Juraj Kuruc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juraj Kuruc updated AMQ-2140:
-----------------------------
Attachment: ttl_amq_bug.zip
> 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:
> « Hide
> WinXP,
> Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
> Reporter: Juraj Kuruc
> Priority: Critical
> 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.
[jira] Updated: (AMQ-2140) Message expriation causes that receiver
gets stuck
Posted by "Juraj Kuruc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juraj Kuruc updated AMQ-2140:
-----------------------------
Environment:
WinXP,
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
was:
« Hide
WinXP,
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
> 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
> Priority: Critical
> 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.
[jira] Issue Comment Edited: (AMQ-2140) Message expriation causes
that receiver gets stuck
Posted by "Fabien Brousse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51801#action_51801 ]
Fabien Brousse edited comment on AMQ-2140 at 5/20/09 6:14 AM:
--------------------------------------------------------------
Tested with 5.2.0, almost same behaviour.
was (Author: fabienbrousse):
Tested with 5.2.0, same behaviour.
> 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
> Priority: Critical
> 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.