[jira] Reopened: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

["Seumas Soltysik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Seumas Soltysik reopened CXF-2398:
----------------------------------


Further testing and reading of the JCA spec indicate that destroying the client proxy when close is called on the ManagedConnection handle returned by ManagedConnection.getConnection() is not appropriate. Doing so causes the proxy to be destroyed more often than necessary. According to the spec, close() is called on the handle proxy created by ManagedConnection.getConnection() before the ManagedConnection is recycled for pooling. Destroying the client proxy at this point is premature. The client proxy itself should be considered the underlying resource and should only be destroyed when the ManagedConnection is itself destroyed. In addition, there is no need to create a client proxy each time getConnection() is called. Each ManagedConnection only requires a single client proxy which in turn can be wrapped by a Connection proxy each time getConnection() is called.

> JMS Connections are not closed when JCA recycles CXF proxy
> ----------------------------------------------------------
>
>                 Key: CXF-2398
>                 URL: https://issues.apache.org/jira/browse/CXF-2398
>             Project: CXF
>          Issue Type: Bug
>          Components: Integration
>    Affects Versions: 2.1
>            Reporter: Seumas Soltysik
>            Assignee: Daniel Kulp
>             Fix For: 2.1.7, 2.2.4
>
>         Attachments: CXF-2398.patch
>
>
> When close() is called on JCA ConnectionHandler, there is no cleanup of the underlying client proxy and its transport. Specfically when the JCA outbound use case is using JMS, JMS connections are not being closed. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.