[ 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
