[
https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746171#action_12746171
]
William Tam edited comment on CXF-2398 at 8/21/09 12:25 PM:
------------------------------------------------------------
OK. I view it differently. The problem with treating handle as you have
described is: if my application calls connection.close(), the application can
still invoke target service without getting an exception until suddenly the
application server calls destroy() on the ManagedConnection. That's not good.
In fact, the handle (i.e. the connection returned by CXFConnectionFactory) is
not being invalidated after cleanup() is called, the application can still call
connection.getService() AND invoke the service without problem. That certainly
does not comply to 6.5.4.4. I guess it is a pre-existed issue.
was (Author: wtam):
OK. I view it differently. The problem with treating handle as you have
described is: if my application calls connection.close(), the application can
still invoke target service without getting an exception until suddenly the
application server calls destroy() on the ManagedConnection. That's not good.
In fact, the handle (i.e. the connection returned by CXFConnectionFactory) is
not being invalidated after cleanup() is called, the application can still call
connection.getService() AND invoke the service without problem. That is
certainly not comply to 6.5.4.4. I guess it is a pre-existed issue.
> 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.
