GaryG wrote: > Here's the tail-end of the activemq.log > ------------------ > 2007-02-20 02:53:13,685 [eckpoint Worker] DEBUG DefaultJDBCAdapter > - Deleted 0 old message(s). > 2007-02-20 02:53:13,685 [eckpoint Worker] DEBUG JDBCPersistenceAdapter > - Cleanup done. > 2007-02-20 02:53:13,685 [eckpoint Worker] DEBUG JournalPersistenceAdapter > - Checkpoint done. > 2007-02-20 02:54:42,690 [34.186.82:35922] DEBUG UsageManager > - Memory usage change. from: 11, to: 12 > 2007-02-20 02:58:43,669 [eckpoint Worker] DEBUG JournalPersistenceAdapter > - Checkpoint started. > 2007-02-20 02:58:43,680 [eckpoint Worker] DEBUG JDBCPersistenceAdapter > - Cleaning up old messages. > 2007-02-20 02:58:43,680 [eckpoint Worker] DEBUG DefaultJDBCAdapter > - Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND > EXPIRATION<?) OR ID <= ( SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM > ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER) > 2007-02-20 02:58:43,681 [eckpoint Worker] DEBUG DefaultJDBCAdapter > - Deleted 0 old message(s). > 2007-02-20 02:58:43,682 [eckpoint Worker] DEBUG JDBCPersistenceAdapter > - Cleanup done. > 2007-02-20 02:58:43,682 [eckpoint Worker] DEBUG JournalPersistenceAdapter > - Checkpoint done. > 2007-02-20 03:01:03,878 [main ] INFO BrokerService > - ActiveMQ Message Broker (amqDev2, > ID:atla-dev-aic2.mss.iss.net-38984-1171932491732-1:0) is shutting down > 2007-02-20 03:01:03,879 [main ] INFO NetworkConnector > - Network Connector default-nc Stopped > ------------------------ > > Following your posted commands, I looked for the Java Service Wrapper > running, and did not see any such process. I couldn't find the wrapper.log > either. I'm assuming from that it's not running. I'm not aware of us ever > using this tool. > > Our OS is RedHat Linux. We're running java version "1.5.0_07" > > _Gary
AMQ 4.1.0 comes with Java Service Wrapper in the standard binary package. It would restart the broker for you. Until you figure out why it's stopping, that may be your best bet. That's definitely a somewhat organized shutdown. It's not just a JVM crash, which wouldn't log anything. (The most stable VM I've run AMQ in was Sun 1.5.0_09, so you may want to try that just in case.) Turn logging up and see where the shutdown init is coming from? (Might want to obfuscate those "iss.net"s. :)) -- Christopher G. Stach II
