Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <11879061.1144425562492.JavaMail.tomcat@stilton>
Date: Fri, 7 Apr 2006 08:59:22 -0700 (PDT)
From: "Niall Stapley (JIRA)" <jira@activemq.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Commented: (AMQ-394) for non-durable topics add a
 configurable Policy to drop messages from slow consumers
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

    [ http://jira.activemq.org/jira//browse/AMQ-394?page=comments#action_35905 ] 

Niall Stapley commented on AMQ-394:
-----------------------------------

We have a similar scenario which would make this feature very useful.

There is a single publisher producing many small messages (to topics) to many (sometimes slow or even stalled) subscribers. The data in the messages  is useful only for about 10 seconds, so we try to use topicPublisher.setTimeToLive(10000) to avoid flow control or broker buffer problems. The messages transmit the latest state and do so regularly so it is not important if delivery of older messages is unreliable for slow consumers, as long as the producer remain unimpeded.

> for non-durable topics add a configurable Policy to drop messages from slow consumers
> -------------------------------------------------------------------------------------
>
>          Key: AMQ-394
>          URL: http://jira.activemq.org/jira//browse/AMQ-394
>      Project: ActiveMQ
>         Type: New Feature

>   Components: Broker
>     Reporter: james strachan
>      Fix For: 4.1

>
>
> e.g. for market data pricing we may wish to only allow say 1000 pending messages but discard old messages rather than have things back up. Similarly we may wish to do something like remove old price changes for the same stock and just keep around the latest prices.
> So some kind of pluggable policy on the non-durable topic subscription would be a good idea, letting users customize this behaviour.
> Maybe some FlowControlPolicy or something?

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