Have you checked the logs for that restarted machine? And maybe you need to setup your clients with a slight reconnect delay?
On Apr 28, 2011, at 3:18 PM, TheFarmer wrote: > I have ActiveMQ running as a Windows service. Windows logs whenever a > service is stopped or started. I am seeing in the logs that the ActiveMQ is > starting up but the windows logs don't show any service restarting at that > time. So it appears that ActiveMQ is restarting by itself. Any idea why or > how to stop this? Here's a log excerpt that shows it restarting. To note > is that there isn't any logging of it stopping. > > 2011-04-19 22:05:31,242 | INFO | RESTful file access application at > http://0.0.0.0:8161/fileserver | org.eclipse.jetty.util.log | > WrapperSimpleAppMain > 2011-04-19 22:05:31,289 | INFO | Started > SelectChannelConnector@0.0.0.0:8161 | org.eclipse.jetty.util.log | > WrapperSimpleAppMain > 2011-04-25 00:28:25,208 | INFO | Refreshing > org.apache.activemq.xbean.XBeanBrokerFactory$1@6f878144: startup date [Mon > Apr 25 00:28:25 UTC 2011]; root of context hierarchy | > org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain > 2011-04-25 00:28:28,474 | INFO | PListStore:E:\Program > Files\ActiveMQ\bin\win32\..\..\data\S601870ATVW28\tmp_storage started | > org.apache.activemq.store.kahadb.plist.PListStore | WrapperSimpleAppMain > 2011-04-25 00:28:28,552 | INFO | Using Persistence Adapter: > KahaDBPersistenceAdapter[E:\Program > Files\ActiveMQ\bin\win32\..\..\data\kahadb] | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2011-04-25 00:28:29,333 | INFO | KahaDB is version 3 | > org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2011-04-25 00:28:29,396 | INFO | Recovering from the journal ... | > org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain > 2011-04-25 00:28:29,396 | INFO | Recovery replayed 2 operations from the > journal in 0.047 seconds. | org.apache.activemq.store.kahadb.MessageDatabase > | WrapperSimpleAppMain > 2011-04-25 00:28:29,599 | INFO | ActiveMQ 5.4.2 JMS Message Broker (abcdef) > is starting | org.apache.activemq.broker.BrokerService | > WrapperSimpleAppMain > 2011-04-25 00:28:29,599 | INFO | For help or more information please see: > http://activemq.apache.org/ | org.apache.activemq.broker.BrokerService | > WrapperSimpleAppMain > 2011-04-25 00:28:29,786 | INFO | Scheduler using directory: E:\Program > Files\ActiveMQ\bin\win32\..\..\data\abcdef\scheduler | > org.apache.activemq.broker.scheduler.SchedulerBroker | WrapperSimpleAppMain > 2011-04-25 00:28:30,536 | INFO | JobSchedulerStore:E:\Program > Files\ActiveMQ\bin\win32\..\..\data\abcdef\scheduler started | > org.apache.activemq.broker.scheduler.JobSchedulerStore | > WrapperSimpleAppMain > 2011-04-25 00:28:30,943 | INFO | Listening for connections at: > tcp://abcdef:61616 | > org.apache.activemq.transport.TransportServerThreadSupport | > WrapperSimpleAppMain > 2011-04-25 00:28:30,943 | INFO | Connector openwire Started | > org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain > 2011-04-25 00:28:30,943 | INFO | ActiveMQ JMS Message Broker (abcdef, > ID:abcdef-55697-1303691309661-0:1) started | > org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain > 2011-04-25 00:28:31,021 | INFO | jetty-7.1.6.v20100715 | > org.eclipse.jetty.util.log | WrapperSimpleAppMain > 2011-04-25 00:28:31,521 | INFO | ActiveMQ WebConsole initialized. | > org.apache.activemq.web.WebConsoleStarter | WrapperSimpleAppMain > 2011-04-25 00:28:32,130 | INFO | Initializing Spring FrameworkServlet > 'dispatcher' | /admin | WrapperSimpleAppMain > 2011-04-25 00:28:32,911 | INFO | ActiveMQ Console at > http://0.0.0.0:8161/admin | org.eclipse.jetty.util.log | > WrapperSimpleAppMain > 2011-04-25 00:28:33,005 | INFO | RESTful file access application at > http://0.0.0.0:8161/fileserver | org.eclipse.jetty.util.log | > WrapperSimpleAppMain > 2011-04-25 00:28:33,036 | INFO | Started > SelectChannelConnector@0.0.0.0:8161 | org.eclipse.jetty.util.log | > WrapperSimpleAppMain > > My problem is that it restarted fast enough that the clients didn't notice > or at least they didn't switch to the failover server but failover server > did take over and become active so I lost messages to the failover with no > one to pick them up. Then I had two servers running until the failover > server restarted on its own... > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-restarting-by-itself-tp3482243p3482243.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
