[
https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746145#action_12746145
]
Seumas Soltysik commented on CXF-2398:
--------------------------------------
Keep in mind that the following structure:
Handle proxy wraps Client proxy wraps Client
As you stated from the spec: "6.5.4.4 says we should invalidate all handles but
at the same time it says cleanup() should not close physical pipe"
For our connector, i chose to treat the Client/ClientProxy as the pipe and the
Handle proxy as the handle. The pipe(Client) is not destroyed on cleanup() but
the handles are released from the map and thus made invalid. So when cleanup is
called, the client remains valid, but the handles are invalid. New handles are
created when the ManagedConnection is re-used and getConnection() is called
again.
> 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.
