activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: Configuring message expiration as a queue policy
Date Tue, 23 Feb 2010 08:47:46 GMT
Hi,

I think TimeStamp plugin will help you in this case
http://activemq.apache.org/timestampplugin.html

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Feb 23, 2010 at 12:08 AM, EnriqueF <efloresc@gmail.com> wrote:

>
> My use case requires that messages on a certain queue expire eventually, as
> stale data will result in damage to customer product. The message producers
> are embedded devices connecting with STOMP. Initially I was using the stomp
> 'expires' header with no success, messages would get dropped immediately..
> until looking at the activeMQ source I realized the expiration needs to be
> set as absolute time instead of relative.. I find this implementation
> choice
> to be very odd, as it requires the client to have clocks synced with the
> broker, but in my application this cannot be relied upon, we have hundreds
> of these devices throughout the production floor.. and if the time and date
> were set wrong, or if the clocks drifted enough, the results would be very
> bad. So my question is, can I instead configure a queue on the broker side
> to enforce a time-to-live policy even if messsages have expires=0?
>
>
> --
> View this message in context:
> http://old.nabble.com/Configuring-message-expiration-as-a-queue-policy-tp27695399p27695399.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message