Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <1053625764.1144425288366.JavaMail.jira@ajax>
Date: Fri, 7 Apr 2006 16:54:48 +0100 (BST)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Resolved: (AMQ-669) Add a keepDurableSubsActive option to
 brokers so that durable subs eagerly loaded and kept in memory
In-Reply-To: <1951401052.1143583714072.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ https://issues.apache.org/activemq/browse/AMQ-669?page=all ]
     
Hiram Chirino resolved AMQ-669:
-------------------------------

    Resolution: Fixed

implemented.  And is on by default now.

> Add a keepDurableSubsActive option to brokers so that durable subs eagerly loaded and kept in memory
> ----------------------------------------------------------------------------------------------------
>
>          Key: AMQ-669
>          URL: https://issues.apache.org/activemq/browse/AMQ-669
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Broker
>     Reporter: Hiram Chirino
>     Assignee: Hiram Chirino
>      Fix For: 4.0 RC3

>
>
> Problem is described at:
> https://issues.apache.org/activemq/browse/AMQ-493
> One way to solve this is to avoid getting to the big backlog of messages.  The there are not too many messages to recover, then AMQ-493 is not an issue.  Add a keepDurableSubsActive option to the broker would be a workaround to this issue.  The down side is that the broker would eventually block if the durable consumer is offline for too long.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira