activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ying (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2286) NetworkConnector PrefetchSize
Date Wed, 10 Jun 2009 20:41:35 GMT

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

ying commented on AMQ-2286:
---------------------------

hi, i tried asyncDispatch=false and optimizeDispatch=true and it did not help.

the real issue we face is when we setup 4 brokers we don't know which broker will be slower.


The reason the consumer on broker2 got stuck might be because the resource it needs to access
is not accessible at the moment. This is a decoupled environment. Applications only know:
talk to a broker and get its task. All of this is not predictable beforehand. That is why
we think PrefetchSize on a networkConnector shall come to rescue but it does not have any
effect at all so far. 

When we found out broker2's consumers are stuck, it is already late because 5000 msg are already
dispatched to the broker.

> NetworkConnector PrefetchSize
> -----------------------------
>
>                 Key: AMQ-2286
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2286
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Sun solaris 10
>            Reporter: ying
>            Priority: Blocker
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message