Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1494062544.1227807245595.JavaMail.jira@brutus>
Date: Thu, 27 Nov 2008 09:34:05 -0800 (PST)
From: "Petr Postulka (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQNET-129) Support for deleting queues and
 durable subcribers.
In-Reply-To: <79060192.1227730745422.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQNET-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47662#action_47662 ] 

Petr Postulka commented on AMQNET-129:
--------------------------------------

Hello Jim,

thanks for your reply and the hint for DeleteDurableConsumer method. The reason why I want to be able delete queues is beacuse I have a situation, where each connected client can not use temporary queue (because can not miss some message and can not receive duplicates), so the only thing which comes in my mind is usage of several queues (each for client) or use Virtual Topic, which leads also to queue per client. Because the number of client can be very large, it is important to delete the queue when the client disconnects.

> Support for deleting queues and durable subcribers.
> ---------------------------------------------------
>
>                 Key: AMQNET-129
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-129
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: ActiveMQ Client
>            Reporter: Petr Postulka
>            Assignee: Jim Gomes
>
> I think that it is very important feature, because now we can delete queues and durable subscribers only manually via JMX, which can not meet requirements in automatic systems. For example if you want to use Publish / Subscribe scenario with durable subscribers, you want to delete the durable subscriber when the client disconnects from the system. Now you can not do it programatically.

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