Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <158923229.1236104279387.JavaMail.jira@brutus>
Date: Tue, 3 Mar 2009 10:17:59 -0800 (PST)
From: "Jim Gomes (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-1803) MirroredQueue cannot be cast to Queue
 when Purging Mirrored Queue
In-Reply-To: <531083149.1213680060276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Jim Gomes updated AMQ-1803:
---------------------------

             Priority: Major  (was: Minor)
    Affects Version/s: 5.2.0

> MirroredQueue cannot be cast to Queue when Purging Mirrored Queue
> -----------------------------------------------------------------
>
>                 Key: AMQ-1803
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1803
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0, 5.2.0
>         Environment: Windows Server 2003 R2 fully patched as of 2008-06-13, Sun Java current version as of 2008-06-13. ActiveMQ 5.1.0 as released as of 2008-05-30.
>            Reporter: Chris Wiegand
>             Fix For: 5.3.0
>
>
> We used MirroredQueues so that we can monitor what's going on using a simple Topic client we wrote. When we click 'Purge' on the queue in the web admin interface, we get a Java exception: org.apache.activemq.broker.region.virtual.MirroredQueue$1 cannot be cast to org.apache.activemq.broker.region.Queue. We are able to delete the queue, but then our listener classes do not auto-reconnect for up to 5 minutes (our own code for that to work around issues with ActiveMQ.Net bindings). 

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