activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GaryG <ggive...@us.ibm.com>
Subject Re: ActiveMQ Broker dying
Date Tue, 20 Feb 2007 17:05:11 GMT

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



James.Strachan wrote:
> 
> On 2/20/07, GaryG <ggiventa@us.ibm.com> wrote:
>>
>> No, I'm not sending any kill commands...
>>
>> I don't even know how to send a kill command to the broker.  And I do not
>> have any JMX consoles open to connect to the process and kill it.
>>
>> Once the broker goes down I get errors like this on the receiver:
>>
>> ----------
>> 2007-02-20 03:01:04,296 [AcitveMQ Connection Worker:
>> tcp://atla-dev-aic2.mss.iss.net/209.134.186.83:61616] ERROR jms_comm -
>> FactoryUtil.onException: javax.jms.JMSException: java.io.EOFException
>> 2007-02-20 03:01:04,296 [AcitveMQ Connection Worker:
>> tcp://atla-dev-aic2.mss.iss.net/209.134.186.83:61616] DEBUG jms_comm -
>> JMS
>> Exception occured. Server is down.
>> ----------
> 
> Is that a client log? Do you get anything in the ActiveMQ broker log?
> -- 
> 
> James
> -------
> http://radio.weblogs.com/0112098/
> 
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQ-Broker-dying-tf3256131s2354.html#a9065926
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message