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:19 UTC
[jira] Created: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
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.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.
[jira] Resolved: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3096.
------------------------------
Resolution: Fixed
> 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
> Assignee: Daniel Kulp
> Fix For: 2.2.12, 2.3.1, 2.4
>
> Attachments: JMSConfiguration.patch
>
>
> 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.
[jira] Assigned: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-3096:
--------------------------------
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> Fix For: 2.2.12, 2.3.1, 2.4
>
> Attachments: JMSConfiguration.patch
>
>
> 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.
[jira] Updated: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
Posted by "Hartmut Lang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hartmut Lang updated CXF-3096:
------------------------------
Attachment: JMSConfiguration.patch
Added a patch that tracks if the SingleConnectionFactory was automatically created inside of the JMSConfiguration.
Only in these cases the factory can be destroyed in the destroyWrappedConnectionFactory() call.
> 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
>
> Attachments: JMSConfiguration.patch
>
>
> 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.
[jira] Updated: (CXF-3096) Closing JMS endpoint always destroys
SingleConnectionFactory
Posted by "Hartmut Lang (JIRA)" <ji...@apache.org>.
[ 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.