[ 
https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746115#action_12746115
 ] 

Seumas Soltysik commented on CXF-2398:
--------------------------------------

I understand your comments regarding a proxy per subject. I would say leave it 
as is for now and open up a jira for the requirement to support the security 
issues you mentioned. However, I disagree with your statement regarding 
cleaning up the proxies in ManagedConnection.cleanup(). Per section 6.5.4.4 of 
the spec:
"It invokes ManagedConnection.cleanup when it has to invalidate all
connection handles associated with this ManagedConnection instance and put the
ManagedConnection instance back in to the pool."
This means that if cleanup() were to destroy the proxies then they would be 
destroyed each time a ManagedConnection was recycled to the pool. Not very 
efficient. The spec talks about the need to hold onto underlying connection 
resources when a ManagedConnection is recycled. In our case, these resources 
are not so clear, but I would contend that the ClientProxy is essentially the 
closest thing to the kind of resources that the spec is talking about. Thus it 
makes sense to hold onto the proxy/proxies until the ManagedConnection is no 
longer needed and destroy() 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, CXF-2398.patch2
>
>
> 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.

Reply via email to