activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-669) Add a keepDurableSubsActive option to brokers so that durable subs eagerly loaded and kept in memory
Date Fri, 07 Apr 2006 13:17:48 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-669?page=all ]

james strachan updated AMQ-669:
-------------------------------

    Fix Version: 4.0 RC3
                     (was: 4.0 RC 2)

> 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


Mime
View raw message