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

List:       activemq-dev
Subject:    [jira] [Resolved] (AMQ-5379) AMQP - allow setting prefetch size
From:       "Dejan Bosanac (JIRA)" <jira () apache ! org>
Date:       2014-11-27 14:08:12
Message-ID: JIRA.12745452.1412242324000.34931.1417097292513 () Atlassian ! JIRA
[Download RAW message or body]


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

Dejan Bosanac resolved AMQ-5379.
--------------------------------
    Resolution: Fixed

Thanks for the comments Robbie. 

The latest commit have the following changes:

- now using producerCredit instead of prefetch in all places related to the producer
- I bumped the default prefetch (and producer credit value) to 1000
- We decided to simplify things in terms of prefetch and credit, as currently we \
can't control it fully. The user can set the value for the prefetch on the transport \
connector and if it does it will be used and not changed. If the value is not set, \
the consumer will use default value until we get the first flow and initial client \
preference. We will use that value afterwards and not change it. I think this is good \
enough for the most current use cases. We can refine logic later with the real use \
                cases.
- The problem with redelivery flag on the messages being set is fixed, as we now \
track the last delivered sequence id and inform the broker on consumer close

> 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
> 
> 
> Currently the prefetch size is hardcoded to the value of 100



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


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