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

ASF subversion and git services commented on AMQ-6267:
------------------------------------------------------

Commit d38c5906f6eadbd20aee97ce37c665b3356dbfd1 in activemq's branch 
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=d38c590 ]

https://issues.apache.org/jira/browse/AMQ-6267

Added two new properties for configuration to a network bridge,
advisoryPrefetchSize and advisoryAckPercentage.  By default
advisoryPrefetchSize is set to 0, which is disabled, and will use the
prefetchSize value unless otherwise set.  Also added validation to
prefetchSize to make sure it is greater than 0 as 0 is not allowed.

(cherry picked from commit 297eadf7461fe4043c81c6f8d806a7c61b680731)


> Allow advisory consumer prefetch configuration for network consumers
> --------------------------------------------------------------------
>
>                 Key: AMQ-6267
>                 URL: https://issues.apache.org/jira/browse/AMQ-6267
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker, networkbridge
>    Affects Versions: 5.13.2
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>             Fix For: 5.14.0
>
>
> In most places the prefetch value for advisory consumers is configured 
> separately than the prefetch value for non-advisory consumers because by 
> default advisory consumers are configured to optimize acknowledgements.  
> However, while the NetworkBridgeConfiguration allows setting prefetchSize it 
> does not allow configuring advisory prefetch size. 
> It would be useful to be able to configure the prefetch size separately for 
> advisory consumers, as well as the percentage of prefetch used for 
> determining when to send back an ack (currently set to 75%)



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

Reply via email to