Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com
 designates 209.85.215.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1367569567335-4666616.post@n4.nabble.com>
References: <1367486640223-4666565.post@n4.nabble.com>
	<01fc01ce4745$5f49a320$1ddce960$@com>
	<1367569567335-4666616.post@n4.nabble.com>
Date: Fri, 3 May 2013 09:10:22 -0700
Message-ID: 
 <CAKS7T5M3R-qwu4NdFMRv5E=TOR649Xw=8xbJVCZXLbc2p8iUsg@mail.gmail.com>
Subject: Re: Durable Topic, only most-recent message needed
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=047d7b3441d68f18fe04dbd29640

--047d7b3441d68f18fe04dbd29640
Content-Type: text/plain; charset=ISO-8859-1

try retroactive consumer and constant pending limit strategy of 1


On Fri, May 3, 2013 at 1:26 AM, Andrea Arcuri <arcuri82@gmail.com> wrote:

> Hi,
>   thanks for reply. Using ActiveMQ  (successfully)  for a lot of different
> types of messages. But that is a particular scenario for one particular
> type
> of message. Adding and installing a database on all nodes of a large system
> of systems of variegated nodes is not a viable option (different OS,
> different programming languages). As ActiveMQ is already installed (or easy
> to install) in all of those nodes, if there was an option to keep/consider
> only the most recent message on a persistent topic, then that would be an
> elegant solution with minimal impact on the current architecture.
>
> cheers
>
> Andrea
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Durable-Topic-only-most-recent-message-needed-tp4666565p4666616.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

--047d7b3441d68f18fe04dbd29640--