You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Christian Tytgat (JIRA)" <ji...@apache.org> on 2014/12/18 10:09:13 UTC
[jira] [Updated] (AMQ-5492) Redelivery count increases on closed
prefetch buffers for topics
[ https://issues.apache.org/jira/browse/AMQ-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Tytgat updated AMQ-5492:
----------------------------------
Description:
This is related to AMQ-1730 which seems to have been fixed for queues but not for topics.
We're running into this problem with a durable topic subscription. The application uses a transacted camel route without CACHE_CONSUMER, so from what I understand, the session gets closed after each receive and all prefetched messages (100 by default) get redispatched by the broker. The broker however is increasing redelivery count and we see lots of messages ending up in the DLQ.
By looking at the implementations of Destination.removeSubscription(ConnectionContext context, Subscription sub, long lastDeliveredSequenceId), it seems that the lastDeliveredSequenceId parameter is only used for queues...
We can workaround this by setting prefetchSize=0 or using CACHE_CONSUMER, but the behavior looks like a issue nevertheless.
was:
This is related to AMQ-1730 which seems to have been fixed for queues but not for topics.
We're running into this problem with a durable topic subscription. The application uses a transacted camel route without CACHE_CONSUMER, so from what I understand, the session gets closed after each receive and all prefetched messages (100 by default) get redispatched by the broker. The broker however is increasing redelivery count and we see lots of messages ending up in the DLQ.
By looking at the implementations of Destination.removeSubscription(ConnectionContext context, Subscription sub, long lastDeliveredSequenceId), it seems that the lastDeliveredSequenceId parameter is only used for queues...
> Redelivery count increases on closed prefetch buffers for topics
> ----------------------------------------------------------------
>
> Key: AMQ-5492
> URL: https://issues.apache.org/jira/browse/AMQ-5492
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.10.0
> Reporter: Christian Tytgat
> Priority: Minor
>
> This is related to AMQ-1730 which seems to have been fixed for queues but not for topics.
> We're running into this problem with a durable topic subscription. The application uses a transacted camel route without CACHE_CONSUMER, so from what I understand, the session gets closed after each receive and all prefetched messages (100 by default) get redispatched by the broker. The broker however is increasing redelivery count and we see lots of messages ending up in the DLQ.
> By looking at the implementations of Destination.removeSubscription(ConnectionContext context, Subscription sub, long lastDeliveredSequenceId), it seems that the lastDeliveredSequenceId parameter is only used for queues...
> We can workaround this by setting prefetchSize=0 or using CACHE_CONSUMER, but the behavior looks like a issue nevertheless.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)