This should only happen if your messages have expiry set on them and by changing times you actually made them expired.
Also, you might find http://activemq.apache.org/timestampplugin.html interesting for cases where clocks between broker and client machines are not in the sync. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Jul 27, 2011 at 8:54 AM, Oscar Pernas <[email protected]> wrote: > Hi all, > > We were making tests of our system and we saw that the time of the broker's > machine was not with the same ntp time that the rest. We changed the time > of > the machine and after that the broker doesn't deliver any more messages. We > are using persistent messages, and I think that is reasonable because > persistent and durable messages could need this UTC time. > > So, what is the procedure if you need to change the time of a machine? if > you shutdown the broker with persistence and pending messages to consume > and > you change the time, could be and problem? if a non-utc time (because > changing times in summer or winter) changes could affect? > > > > regards!! > > -- > Óscar Pernas Plaza. >
