On Tue, Aug 17, 2010 at 11:44 AM, Bruce Snyder <bruce.sny...@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 2:53 AM, p-fx <shmulik...@gmail.com> wrote:
>>
>> Hello.
>> I am using ActiveMQ as message Broker with something like 140 Topics.
>> I am facing a problem that the broker keeps old messages, instead of
>> discarding them in order to send new messages (so clients gets old data
>> instead of current data).
>> How do I configure the broker not to keep old messages? the important data
>> is allways the last data, so if a consumer didn't get data, he will get next
>> time the most updated.
>> I have configured on producer TTL as 250, but it doesn't seem to work...
>> One other thing,
>> How can I disable the creation of advisory topics?
>>
>> Any help will be appreciated...
>
> If you have set the timeToLive on the producer, then the messages
> should be expired in the broker. What version of ActiveMQ are you
> using?
>
> Also, given your requirements, you might want to consider setting up
> an eviction policy:
>
> http://activemq.apache.org/slow-consumer-handling.html
BTW, if you enable debug logging, you will see messages like the
following showing the thread that expires messages:
2010-08-17 11:58:52,777 | DEBUG | Expiring messages .. |
org.apache.activemq.broker.region.Queue | ActiveMQ Scheduler
Bruce
--
perl -e 'print
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
