You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Hartmut Lang (JIRA)" <ji...@apache.org> on 2010/10/27 07:34:20 UTC
[jira] Updated: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
[ https://issues.apache.org/jira/browse/CXF-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hartmut Lang updated CXF-3096:
------------------------------
Fix Version/s: 2.2.12
> Closing JMS endpoint always destroys SingleConnectionFactory
> ------------------------------------------------------------
>
> Key: CXF-3096
> URL: https://issues.apache.org/jira/browse/CXF-3096
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Hartmut Lang
> Fix For: 2.2.12, 2.3.1, 2.4
>
>
> On calling close() on a JMSConduit or calling shutdown() on a JMSDestination the used SingleConnectionFactory gets always destroyed.
> This must not be done in any cases because the same SingleConnectionFactory might be used by other JMS endpoints (e.g. if configured in using the JMSConfig-Feature).
> This should be fixed in a way that the JMSConfig should record if it automatically has created the SingleConnectionFactory(e.g. JNDI use-case), only in this case it should be destroyed.
> Also see: CXF-2788
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.