[
https://issues.apache.org/jira/browse/AMQ-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5710.
--------------------------------
Resolution: Fixed
Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/c705523c
> ActiveMQConnection cleanup should not close the connection on the broker
> ------------------------------------------------------------------------
>
> Key: AMQ-5710
> URL: https://issues.apache.org/jira/browse/AMQ-5710
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.12.0
>
>
> As the spec says
> http://docs.oracle.com/javaee/6/api/javax/resource/spi/ManagedConnection.html#cleanup()
> "The cleanup of ManagedConnection instance resets its client specific state
> and prepares the connection to be put back in to a connection pool. The
> cleanup method should not cause resource adapter to close the physical pipe
> and reclaim system resources associated with the physical connection."
> We should not send RemoveInfo on cleanup, but just clean client side state.
> The result of "closing" a connection on cleanup is that connection will not
> be cached when using XA transactions, causing high CPU usage on the broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
