activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1633) Temporary destinations not being cleaned up upon delete() when using network of brokers
Date Tue, 01 Apr 2008 06:52:32 GMT

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

Rob Davies resolved AMQ-1633.
-----------------------------

    Fix Version/s: 5.1.0
       Resolution: Fixed

> Temporary destinations not being cleaned up upon delete() when using network of brokers
> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-1633
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1633
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: N/A
>            Reporter: Ari Cooperman
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> When deleting a temp destination a DestinationInfo object is sent signifying the deletion
to brokers. These are not deleted immediately but are instead put into the cachedDestinations
map in AbstractTempRegion. Upon the regular scheduled doPurge call any that are older than
a minute are disposed of, however, calling remove on the cache map returns nothing because
the key object, CachedDestination has a bug inside the equals method in the instanceof check
and the temp destinations stick around and are never disposed of
>             if (o instanceof ActiveMQDestination) {
> Should be 
>             if (o instanceof CachedDestination ) {

-- 
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