Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <7802754.71301291295501729.JavaMail.jira@thor>
Date: Thu, 2 Dec 2010 08:11:41 -0500 (EST)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-2176) Time out for Durable Subscribers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dejan Bosanac updated AMQ-2176:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> Time out for Durable Subscribers
> --------------------------------
>
>                 Key: AMQ-2176
>                 URL: https://issues.apache.org/jira/browse/AMQ-2176
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>         Environment: all
>            Reporter: Andreas Gies
>            Priority: Minor
>             Fix For: 5.5.0
>
>
> This feature comes from practical considerations. Imagine consumers that create durable subscribers on a broker. If those consumers die unexpectedly and are not revived, the durable subscription continues to exist and messages sent to the according topic will be stored persistently. I propose to have an enhanced version of the createDurableSubscriber method accepting an addtional parameter with a timeout value. The intended behavior on the broker side is to drop a durable 
> subscription if no active subscriber has been connected within the given timeout value. By default the feature should be turned off.

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