[
https://issues.apache.org/jira/browse/SM-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned SM-1964:
----------------------------------------
Assignee: Jean-Baptiste Onofré (was: Chris Custine)
> JMS Flow only uses one connection even with a PooledConnectionFactory
> ---------------------------------------------------------------------
>
> Key: SM-1964
> URL: https://issues.apache.org/jira/browse/SM-1964
> Project: ServiceMix
> Issue Type: Improvement
> Affects Versions: 3.3.2
> Reporter: Hadrian Zbarcea
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.3.3
>
> Attachments: PooledConnectionFix.patch, sm-1964-2.patch,
> smx-1964.patch
>
>
> The AbstractJMSFlow uses only one connection for routing. It should take
> advantage of a connection pool if that's the case, but there is a bit of an
> edge case where this is actually a more severe issue.
> If the flow is defined such that:
> * during the flow messages are produced and send back to a queue and
> * a failover transport is used (which uses a MutexTransport internally) and
> * the broker where we enqueue is slow
> then the producer will wait for the slow broker, but in the meantime will
> hold the mutex, preventing all the consumers in all the threads to consume
> which will lead (potentially) to queues filling up on the broker and pretty
> much everything grinding to a halt.
> Proposed patch to follow shortly.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
