Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <23108735.1201694965569.JavaMail.jira@brutus>
Date: Wed, 30 Jan 2008 04:09:25 -0800 (PST)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Assigned: (AMQCPP-161) CMS does not support prefetchSize=0
 correctly
In-Reply-To: <18449403.1201538005319.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Timothy Bish reassigned AMQCPP-161:
-----------------------------------

    Assignee: Timothy Bish  (was: Nathan Mittler)

> CMS does not support prefetchSize=0 correctly
> ---------------------------------------------
>
>                 Key: AMQCPP-161
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-161
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.1.2
>            Reporter: Dominic Tulley
>            Assignee: Timothy Bish
>             Fix For: 2.2
>
>         Attachments: main.cpp
>
>
> AMQ-850 introduced the ability to set the message prefetch size to 0.
> This means that no messages are prefetched and every receive() call goes all the way to the broker to get the next message.
> It was only a valid option for synchronous message receivers.
> In CMS it does not appear to work.  Instead, a client set to use this simply receives no messages, and the messages remain on the queue.
> Without this patch, it is possible for a slow consumer to hide an important message from other consumers because it has prefetched it.

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