activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Luo (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2349) Temporary destinations created with PooledConnectionFactory never get deleted
Date Thu, 06 Aug 2009 16:28:35 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe Luo updated AMQ-2349:
-------------------------

    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.

  was:
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 created with PooledConnectionFactory never get deleted
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2349
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2349
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Joe Luo
>         Attachments: tempDestination-trunk.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message