[
https://issues.apache.org/jira/browse/CXF-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254574#comment-14254574
]
CXFuser1 commented on CXF-6156:
-------------------------------
Thanks Daniel. I will try that. However later I debugged the JMSCOnduit code
and realized that the code does call JMSUtils.closeConnection and the
connection does get closed when the calls are made from webcontaner.
However when the call to webservice is is made via the EJB Container even
though JMSUtils.closeconnection is called the connections are not closed. It
just happens that JMSConduit.finalize method gets called by JVM which cleans up
the beans, and if it doesnt than the bean is dirty and cannot be reused again
unless the server is started(connection is stuck).
Do you have any advice on if we continue to use 2.6.11 how would you expect
these connections to be closed via EJB . I dont think upgrading to higher
version would help in this case.
Thanks again.
> JMS Conduit calling Spring Connection Factory close only through Finalize
> -------------------------------------------------------------------------
>
> Key: CXF-6156
> URL: https://issues.apache.org/jira/browse/CXF-6156
> Project: CXF
> Issue Type: Test
> Components: JMS
> Affects Versions: 2.6.11
> Reporter: CXFuser1
> Fix For: NeedMoreInfo
>
>
> Hi,
> I am using apache cxf 2.6.11 with
> org.apache.cxf.transport.jms.JMSConfiguration.
> which internally creates SingleConnectionFactory.initconnection eveytime a
> request is made.
> However the connections are only closed after the Conduit.finalize is called.
> I am not sure whats incorrect in my configuration. have tried researching for
> quite some time now.
> Any help is appreciated
> Thanks
> Tia
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
