[jira] Commented: (SM-1964) JMS Flow only uses one connection even with a PooledConnectionFactory

["Hadrian Zbarcea (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60633#action_60633 ] 

Hadrian Zbarcea commented on SM-1964:
-------------------------------------

Patch attached, I'll try to put together a unit test as well.

> JMS Flow only uses one connection even with a PooledConnectionFactory
> ---------------------------------------------------------------------
>
>                 Key: SM-1964
>                 URL: https://issues.apache.org/activemq/browse/SM-1964
>             Project: ServiceMix
>          Issue Type: Improvement
>    Affects Versions: 3.3.2
>            Reporter: Hadrian Zbarcea
>             Fix For: 3.3.3
>
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.