[ https://issues.apache.org/activemq/browse/AMQ-792?page=all ]
james strachan resolved AMQ-792:
--------------------------------
Fix Version: 4.1
(was: 4.2)
Resolution: Fixed
For details see:
http://incubator.apache.org/activemq/consumer-dispatch-async.html
basically you can enable async dispatching on all consumers or on a specific
consumer for something which is likely to be a slow consumer to avoid one
blocked consumer slowing the delivery to other consumers (assuming you have a
large enough thread pool)
> allow asynchronous dispatch to consumers in the broker for non-durable topics
> -----------------------------------------------------------------------------
>
> Key: AMQ-792
> URL: https://issues.apache.org/activemq/browse/AMQ-792
> Project: ActiveMQ
> Type: Improvement
> Components: Broker
> Reporter: james strachan
> Fix For: 4.1
>
>
> We typically use the current thread in the broker to dispatch to all the
> available non-durable consumers for performance - as this hugely reduces the
> context switching and increases performance. However (see AMQ-688) sometimes
> this can cause one dead consumer to block a producer.
> Some folks may want to switch this strategy to use slower asynchronous
> dispatch with a thread pool to reduce the risk of blocking a producer at the
> expensive of lower performance
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
