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. ---------- James.Strachan wrote: > > On 2/20/07, GaryG <[EMAIL PROTECTED]> 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 > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/ActiveMQ-Broker-dying-tf3256131s2354.html#a9064517 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
