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 allowed to traverse before being delivered to an end consumer; I think you're talking about message expiration instead, hence the suggestion above about the TimeStampPlugin. On Wed, Oct 1, 2014 at 2:53 PM, coryplusplus <coryplusp...@gmail.com> wrote: > 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. >
