[
https://issues.apache.org/jira/browse/AMQ-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287324#comment-14287324
]
Dejan Bosanac commented on AMQ-5534:
------------------------------------
There's a new {{reconnectOnException}} property on the pooled connection
factory (true by default). It will cause a new ExceptionListener to be
registered on underlying connection and dispose the connection from the pool
when problem is detected.
> 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)
