CXF
  1. CXF
  2. CXF-3096

Closing JMS endpoint always destroys SingleConnectionFactory

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.12, 2.3.1, 2.4
    • Component/s: Transports
    • Labels:
      None

      Description

      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

        Activity

        Hide
        Hartmut Lang added a comment -

        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.

        Show
        Hartmut Lang added a comment - 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.

          People

          • Assignee:
            Daniel Kulp
            Reporter:
            Hartmut Lang
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development