Hi, One important thing was when I was trying to start the broker after time has changed, it cant start and in traces I could see something like this:
2011-07-20 17:44:33,062 | INFO | ActiveMQ Message Broker (localhost, ID:momsn-1559-1311197342093-0:1) is shutting down | org.apache.activemq.broker.BrokerService | Thread-21 2011-07-20 17:44:33,078 | INFO | ActiveMQ Message Broker (localhost, ID:momsn-1559-1311197342093-0:1) is shutting down | org.apache.activemq.broker.BrokerService | ActiveMQ ShutdownHook 2011-07-20 17:44:33,109 | INFO | Connector openwire Stopped | org.apache.activemq.broker.TransportConnector | ActiveMQ ShutdownHook 2011-07-20 17:44:33,109 | INFO | Connector openwire Stopped | org.apache.activemq.broker.TransportConnector | Thread-21 2011-07-20 17:44:33,140 | INFO | PListStore:C:\apache-activemq-5.4.2\data\localhost\tmp_storage stopped | org.apache.activemq.store.kahadb.plist.PListStore | Thread-21 2011-07-20 17:44:33,140 | WARN | Failed to remove consumer: ID:momsn-1559-1311197342093-2:1:1:1. Reason: org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped: org.apache.activemq.broker.BrokerService$3@18c14b3 | org.apache.activemq.broker.TransportConnection | ActiveMQ Task org.apache.activemq.broker.BrokerStoppedException: Broker has been stopped: org.apache.activemq.broker.BrokerService$3@18c14b3 Is this warnings relationated with time changes? regards 2011/7/27 Dejan Bosanac <[email protected]> > 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. > > > -- Óscar Pernas Plaza.
