I'm seeing a similar issue here. I'm using a standard 5.1 distribution and simply starting it up and sending a couple hundred messsages a minute on 1 topic with 6 subscribers. After some arbitrary length of time - it managed just over a day last time round - the server shuts down with no explanation. Just this in the log:
2008-07-10 20:06:09,061 [MQ ShutdownHook] INFO BrokerService - ActiveMQ Message Broker (localhost, ID:the.feedsportal.com-41032-1215612960298-0:0) is shutting down 2008-07-10 20:06:09,061 [MQ ShutdownHook] INFO NetworkConnector - Network Connector default-nc Stopped 2008-07-10 20:06:09,798 [127.0.0.1:61616] WARN FailoverTransport - Transport failed to tcp://localhost:61616 , attempting to automatically reconnect due to: java.io.EOFException 2008-07-10 20:06:09,816 [MQ ShutdownHook] INFO TransportConnector - Connector openwire Stopped 2008-07-10 20:06:11,173 [MQ ShutdownHook] INFO TransportConnector - Connector ssl Stopped 2008-07-10 20:06:13,173 [MQ ShutdownHook] INFO TransportConnector - Connector stomp Stopped 2008-07-10 20:06:13,797 [MQ ShutdownHook] INFO TransportConnector - Connector xmpp Stopped 2008-07-10 20:06:13,824 [MQ ShutdownHook] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:the.feedsportal.com-41032-1215612960298-0:0) stopped Is there any additional logging I can enable that would offer some sort of clue as to what's going on? Regards Andy Wu dolphin_cheng wrote: > > Oh sorry, I paste the wrong log. This is the log of AMQ4.1,and it didn't > running steadily. So we use 5.1 instead. unfortunately, it is also not > steady. The log of 5.1 is the same as 4.1 I paste before. > > rajdavies wrote: >> >> That looks like you're using ActiveMQ 4.1 - want to try 5.1 instead ? >> >> On 11 Jun 2008, at 12:35, dolphin_cheng wrote: >> >>> >>> Yes, there is nothing in the logs from Activemq to indicate why it >>> failed. >>> In the logs from our project there is only exception "Could not >>> connect to >>> broker URL: tcp://159.226.2.169:61616?wireFormat. >>> maxInactivityDuration=0. Reason: java.net.ConnectException: Connection >>> refused". >>> I paste the content of start.out of AMQ: >>> ACTIVEMQ_HOME: /home/agrid/activemq >>> Loading message broker from: xbean:activemq.xml >>> INFO BrokerService - ActiveMQ 4.1.0-incubator JMS >>> Message >>> Broker (localhost) is starting >>> INFO BrokerService - For help or more information >>> please >>> see: http://incubator.apache.org/activemq/ >>> INFO ManagementContext - JMX consoles can connect to >>> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi >>> INFO JDBCPersistenceAdapter - Database driver recognized: >>> [apache_derby_embedded_jdbc_driver] >>> INFO DefaultDatabaseLocker - Attempting to acquire the >>> exclusive >>> lock to become the Master broker >>> INFO DefaultDatabaseLocker - Becoming the master on >>> dataSource: >>> [EMAIL PROTECTED] >>> INFO JournalPersistenceAdapter - Journal Recovery Started >>> from: Active >>> Journal: using 5 x 20.0 Megs at: /home/agrid/activemq/activemq-data/ >>> journal >>> INFO JournalPersistenceAdapter - Journal Recovered: 19 >>> message(s) in >>> transactions recovered. >>> INFO TransportServerThreadSupport - Listening for connections at: >>> tcp://condor.sdg.ac.cn:61616?wireFormat.maxInactivityDuration=0 >>> INFO TransportConnector - Connector openwire Started >>> INFO TransportServerThreadSupport - Listening for connections at: >>> ssl://condor.sdg.ac.cn:61617 >>> INFO TransportConnector - Connector ssl Started >>> INFO TransportServerThreadSupport - Listening for connections at: >>> stomp://condor.sdg.ac.cn:61613 >>> INFO TransportConnector - Connector stomp Started >>> INFO NetworkConnector - Network Connector default-nc >>> Started >>> INFO BrokerService - ActiveMQ JMS Message Broker >>> (localhost, ID:condor.sdg.ac.cn-38555-1213168854805-1:0) started >>> INFO BrokerService - ActiveMQ Message Broker >>> (localhost, >>> ID:condor.sdg.ac.cn-38555-1213168854805-1:0) is shutting down >>> INFO NetworkConnector - Network Connector default-nc >>> Stopped >>> INFO TransportConnector - Connector openwire Stopped >>> INFO TransportConnector - Connector ssl Stopped >>> INFO TransportConnector - Connector stomp Stopped >>> INFO BrokerService - ActiveMQ JMS Message Broker >>> (localhost, ID:condor.sdg.ac.cn-38555-1213168854805-1:0) stopped >>> >>> >>> rajdavies wrote: >>>> >>>> There's nothing in the logs from ActiveMQ to indicate why it failed ? >>>> >>>> On 11 Jun 2008, at 08:02, dolphin_cheng wrote: >>>> >>>>> >>>>> We use activemq 5.1.0 and deploy it in a linux system. Several >>>>> days ago, I >>>>> asked a question that EOFException can lead to broker shut down. But >>>>> I found >>>>> that even there is no EOFException the broker can shut down too. We >>>>> are >>>>> waiting for the solution vexedly, please help us ^_^ >>>>> Thanks very much！！ >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/ActiveMQ-Message-Broker-shut-down-without-Exception-tp17771296p17771296.html >>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>>> >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/ActiveMQ-Message-Broker-shut-down-without-Exception-tp17771296p17775480.html >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>> >> >> >> > > -- View this message in context: http://www.nabble.com/ActiveMQ-Message-Broker-shut-down-without-Exception-tp17771296p18399847.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
