You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/02/06 14:30:42 UTC
[jira] [Closed] (AMQ-5611) Removed queue is resurrected after
master restart
[ https://issues.apache.org/jira/browse/AMQ-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon closed AMQ-5611.
---------------------------------------
Resolution: Won't Fix
LevelDB has been deprecated and is no longer supported.
> Removed queue is resurrected after master restart
> -------------------------------------------------
>
> Key: AMQ-5611
> URL: https://issues.apache.org/jira/browse/AMQ-5611
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
> Affects Versions: 5.11.0, 5.11.1
> Environment: jdk1.7.0_75, Debian 3.16.7
> Reporter: Artem Karpenko
>
> In a setup of broker cluster with 3 ActiveMQ nodes and 1 Zookeeper instance (also reproduced with 3 ZKs) with persistence configured to use Replicated LevelDB removal of queue does not persist after master restart.
> Steps to reproduce:
> # Send a message to a queue A1
> # Consume messages from queue A1
> # Delete queue using via UI
> # Restart master
> # Observe removed queue in console
> This is also reproduced when configuring automatic deletion of queues after inactivity: logs indicate that queue is deleted and it disappears from UI but restart of master node make it reappear.
> This seems to be the same issue in behaviour as AMQ-4970, though persistence layers differ.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)