activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Updated: (AMQ-2286) NetworkConnector PrefetchSize
Date Wed, 22 Jul 2009 15:57:33 GMT


Gary Tully updated AMQ-2286:

    Priority: Major  (was: Blocker)

changing priority to major as I don't think this issue should block a 5.3 release. 

The prefetch is in effect for a network consumer but the consumer dispatches immediately to
a broker through a message producer that does not block unless the send blocks through a memory
utilization limit.  Thus my previous comments. Constraining the queue's memory usage should
block message producers for slow brokers.

Have you had any success with memory usage or disk usage constraints that will cause a send
to block pending space?

> NetworkConnector PrefetchSize
> -----------------------------
>                 Key: AMQ-2286
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Sun solaris 10
>            Reporter: ying
> I have an issue which greatly reduces the quality of service of a network of activemq
> 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 is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message