activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GaryG <>
Subject Re: ActiveMQ Broker dying
Date Tue, 20 Feb 2007 15:56:58 GMT

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://] ERROR jms_comm -
FactoryUtil.onException: javax.jms.JMSException:
2007-02-20 03:01:04,296 [AcitveMQ Connection Worker:
tcp://] DEBUG jms_comm - JMS
Exception occured. Server is down.

James.Strachan wrote:
> On 2/20/07, GaryG <> wrote:
>> I am not using a Java Service Wrapper. Not sure what that is.
>> Broker just died again last night.
>> I am using the broker as installed, just from command line, with the only
>> modifications to the config file being the turning off of the shutdown
>> hook,
>> adding jmx, and commenting out the network connector stuff.  Literally
>> it's
>> pretty much out of the box.
>> This is absolutely critical for our system, I don't understand why the
>> broker just dies, and this has been happening regularly!  I know it's not
>> due to a rogue "control-C" being pressed (had those issues too and fixed
>> them by disabling the shutdown hook)
> You sure noones sending it kill signals or using JMX to shut it down?
> I've never seen a broker just stop before, particularly with no errors.
> Whats your platform?
>> Does the broker HAVE to be used as "embedded" in a java process to keep
>> it
>> from dying?
> Its Java so you can embed it in any JVM you like, or use the command line
> tools.
> -- 
> James
> -------

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message