You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2022/02/16 20:57:00 UTC

[jira] [Updated] (AMQ-2286) NetworkConnector PrefetchSize

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

Matt Pavlovich updated AMQ-2286:
--------------------------------
    Labels:   (was: close-pending)

> NetworkConnector PrefetchSize
> -----------------------------
>
>                 Key: AMQ-2286
>                 URL: https://issues.apache.org/jira/browse/AMQ-2286
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Sun solaris 10
>            Reporter: ying
>            Priority: Major
>             Fix For: 5.x
>
>
> I have an issue which greatly reduces the quality of service of a network of activemq brokers.
> Here is what I have:
> 1. 4 brokers( broker1, broker2, broker3,  broker4) in a network by multicast discovery
> 2. i have 2 consumers of QueueA on broker1, 2 consumers of QueueA on broker2, and consumer queuePrefetch=1, networkConnector prefetchSize=1. Queue is using RoundRobinDispatchPolicy
> 3. I publish to QueueA on broker3 with 100 msgs, 2 consumers on broker1 are fast and they process fine but 2 consumers on broker2 are stuck. However, with this config, msgs are still 50 goes to broker1, 50 goes to broker2, and when consumers on broker2 get stuck, those 50 msgs are stuck on broker2. It seems the prefetchSize=1 on networkConnector have no effect at all.
> what I expect in this case will be that 98 msgs shall go to broker1, and only 2 msgs stuck on broker2's consumers. I cannot lose a single msg so ConstantPendingMessageLimit will not help.
> Please help. Thanks



--
This message was sent by Atlassian Jira
(v8.20.1#820001)