ActiveMQ
  1. ActiveMQ
  2. AMQ-2349

Temporary destinations created with PooledConnectionFactory never get deleted

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.6.0
    • Component/s: Broker
    • Labels:
      None

      Description

      Temporary destinations that created are bound to the underlying connection. If the connection is destroyed, then the temp destinations that bound to the connection will be destroyed.

      In the case that a PooledConnectionFactory is used, the underlying connection won't be destroyed even though PooledConnection.close() is called. Instead it is returned back to the pool. Thus, the temp desinations that created would never be destroyed and all of them would be accumulated until the connection is destroyed.

      We should delete the temp destinations every time when the PooledConnection.close() is called to avoid accumulation of the temporary destinations.

        Activity

        Joe Luo created issue -
        Joe Luo made changes -
        Field Original Value New Value
        Attachment tempDestination-trunk.patch [ 18266 ]
        Joe Luo made changes -
        Description Temporary destinations that created are bound to the underlying connection. If the connection is destroyed, then the temp destinations that bound to the connection will be destroyed.

        In the case that a PooledConnectionFactory is used, the underlying connection won't be destroyed even though PooledConnection.close() is called. Instead it is returned back to the pool. Thus, the temp desinations that created would never be destroyed and all of them would be accumulated until the connection is destroyed.

        We should delete the temp destinations every time when the PooledConnection.close() is called.
        Temporary destinations that created are bound to the underlying connection. If the connection is destroyed, then the temp destinations that bound to the connection will be destroyed.

        In the case that a PooledConnectionFactory is used, the underlying connection won't be destroyed even though PooledConnection.close() is called. Instead it is returned back to the pool. Thus, the temp desinations that created would never be destroyed and all of them would be accumulated until the connection is destroyed.

        We should delete the temp destinations every time when the PooledConnection.close() is called to avoid accumulation of the temporary destinations.
        Rob Davies made changes -
        Fix Version/s 5.4.1 [ 12332 ]
        Bruce Snyder made changes -
        Fix Version/s 5.5.0 [ 12344 ]
        Fix Version/s 5.4.1 [ 12332 ]
        Jeff Turner made changes -
        Project Import Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]
        Dejan Bosanac made changes -
        Fix Version/s 5.5.0 [ 12315626 ]
        Fix Version/s 5.4.2 [ 12315625 ]
        Gary Tully made changes -
        Fix Version/s 5.6.0 [ 12316331 ]
        Fix Version/s 5.5.0 [ 12315626 ]
        Timothy Bish made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Timothy Bish [ tabish121 ]
        Resolution Fixed [ 1 ]
        Gary Tully made changes -
        Fix Version/s 5.6.0 [ 12317974 ]
        Fix Version/s 5.x [ 12316331 ]

          People

          • Assignee:
            Timothy Bish
            Reporter:
            Joe Luo
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development