[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Assigned: (AMQ-1201) Durable topic message delivery to
From:       "Rob Davies (JIRA)" <jira () apache ! org>
Date:       2007-07-31 5:51:50
Message-ID: 20094255.1185861110178.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Rob Davies reassigned AMQ-1201:
-------------------------------

    Assignee: Rob Davies

> Durable topic message delivery to restarted consumer results in messages out of \
>                 order.
> --------------------------------------------------------------------------------------
>  
> Key: AMQ-1201
> URL: https://issues.apache.org/activemq/browse/AMQ-1201
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Reporter: Kevin Yaussy
> Assignee: Rob Davies
> Fix For: 5.0.0
> 
> 
> While testing AMQ 4.2 SNAPSHOT from 3/9, I can create the situation wherein a \
> consumer that was killed and then restarted will get the "prefetchLimit" # of \
> messages last, which means they are out of order. setup:
> 1 Broker
> Consumer on Durable topic, prefetchSize=20
> Publisher publishes to Durable topic
> Let some messages flow, then kill off Consumer.  Let a few thousand messages queue \
> up, then restart the consumer. The Broker begins redelivery of messages, and then \
> when it gets down to the end of the queue, the very first 20 messages from when the \
> Consumer first went down are delivered.  This means that those messages come out of \
> order.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]