I just read your other message where you indicate you're already aware of
the TimeStampPlugin, so disregard that suggestion.
On Fri, Oct 3, 2014 at 12:44 PM, Tim Bain wrote:
> The TimeStampPlugin (http://activemq.apache.org/timestampplugin.html)
> will allow broker clocks to override the JMS tim
The TimeStampPlugin (http://activemq.apache.org/timestampplugin.html) will
allow broker clocks to override the JMS timestamp on the message, ignoring
faulty client clock; is that what you're looking for?
Note that "timeToLive" in ActiveMQ generally refers to the number of
brokers a message is allo
Was a solution ever found for this particular problem. I am experiencing the
exact same scenario.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/timeToLive-with-out-of-sync-clocks-tp3009739p4686072.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks,
I did try putting in the timestamp plugin. It did not seem to fix the
problem.
to reproduce: use a broker and a producer on one box with the correct time.
use a subscriber on another box with a clock 3 minutes ahead. producer sends
a message with a TTL of 2 minutes, and subscriber does no
Have you looked at the timestampPlugin -
http://activemq.apache.org/timestampplugin.html ?
On 25 Oct 2010, at 06:04, simevans wrote:
>
> We are using activemq 5.3.2. We noticed our subscriber does not receive
> messages when the clock on the subscriber is out by more that the timeToLive
> that
Hi,
you can add timestamp plugin
(http://activemq.apache.org/timestampplugin.html), which will sync the
message with the broker's time.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog -
