[
https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746178#action_12746178
]
Seumas Soltysik commented on CXF-2398:
--------------------------------------
6.5.4.4
"The container always drives the cleanup of a ManagedConnection instance. The
container keeps track of created connection handles in an implementation
specific
mechanism. 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 may be called after the end
of a connection sharing scope or when the last associated connection handle is
closed
for a ManagedConnection instance."
My reading of this is that it is up to the container to make sure that after
close() is called, the handles will not longer be used. However, to be sure,
when close() is called on the handle we could set a member variable to indicate
that the handle has been closed and any further calls to invoke() on the proxy
handler could throw an exception.
> 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.
