Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 2 Dec 2014 15:27:12 +0000 (UTC)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12745452.1412242324000.58927.1417534032790@Atlassian.JIRA>
In-Reply-To: <JIRA.12745452.1412242324000@Atlassian.JIRA>
References: <JIRA.12745452.1412242324000@Atlassian.JIRA>
 <JIRA.12745452.1412242324306@arcas>
Subject: [jira] [Commented] (AMQ-5379) AMQP - allow setting prefetch size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231618#comment-14231618 ] 

Dejan Bosanac commented on AMQ-5379:
------------------------------------

Yeah, I also agree with it. The thing is that when I was trying to do that against 0.26 clients, I never got any flow from the client until I send something to it first. Also, setting the prefetch using transport.prefetch option is only for this legacy client as well. We have users that want to use 0.26 clients and control the prefetch, so that's the only way I managed to make it work.

Let me try to write some test that demonstrates this initial prefetch 0 problem with 0.26 client, and maybe we can give it a more thought on how to make it work.

> AMQP - allow setting prefetch size
> ----------------------------------
>
>                 Key: AMQ-5379
>                 URL: https://issues.apache.org/jira/browse/AMQ-5379
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.10.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.11.0
>
>         Attachments: 0001-AMQ-5379-inspect-the-actual-total-credit-rather-than.patch
>
>
> Currently the prefetch size is hardcoded to the value of 100


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)