[
https://issues.apache.org/jira/browse/AMQ-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-6290.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.13.4
> JMS Pool reconnection logic not always reliable
> -----------------------------------------------
>
> Key: AMQ-6290
> URL: https://issues.apache.org/jira/browse/AMQ-6290
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-pool, JMS client
> Affects Versions: 5.13.0, 5.13.1, 5.13.2, 5.13.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.14.0, 5.13.4
>
>
> The reconnect on exception configuration setting in the JMS pool relies on an
> exception being thrown from the ExceptionListener to signal a reconnect
> needed. This can miss an exception thrown from the start method when the
> initial connection attempt is being made and things like security exceptions
> trigger connection failure. Even if the exception is given to the listener
> it happens asynchronously which means the pool will be handling out known
> broken connection instances until the listener gets around to running the
> close logic.
> For the start method we should also be handling the exception in
> ConnectionPool and checking for the reconnect on exception flag to indicate a
> failure has occurred and the Connection should be closed and evicted from the
> pool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
