[jira] [Commented] (AMQ-5534) Generic JMS connection pool should be able to renew connections after JMSException

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-5534:
------------------------------------------------------

Commit b65c0d1be4b0812229d3f166e50d963766856c53 in activemq's branch refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b65c0d1 ]

https://issues.apache.org/jira/browse/AMQ-5510
https://issues.apache.org/jira/browse/AMQ-5534

PooledConnectioFactory added reconnection support but can break if the
holder of the connection adds their own ExceptionListener as the
PooledConnection doesn't protect the internal ExceptionListener from
replacement which leads to cases where the loaned Connection is not
automatically closed so that the next create returns the same failed
connection.  

> Generic JMS connection pool should be able to renew connections after JMSException
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-5534
>                 URL: https://issues.apache.org/jira/browse/AMQ-5534
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool
>    Affects Versions: 5.10.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.11.0
>
>
> The generic jms pool does not have a mechanism to detect connection failure and dispose those connections. Adding a jms exception listener that will do that will do the trick.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)