Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A11B7D115 for ; Mon, 29 Oct 2012 12:07:39 +0000 (UTC) Received: (qmail 82321 invoked by uid 500); 29 Oct 2012 12:07:38 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 82283 invoked by uid 500); 29 Oct 2012 12:07:38 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 82251 invoked by uid 99); 29 Oct 2012 12:07:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 12:07:37 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 12:07:32 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TSo7a-0003Ve-VC for users@activemq.apache.org; Mon, 29 Oct 2012 05:07:11 -0700 Date: Mon, 29 Oct 2012 05:07:10 -0700 (PDT) From: ndmigration To: users@activemq.apache.org Message-ID: <1351512430959-4658373.post@n4.nabble.com> In-Reply-To: <8261914C-74DB-4699-B03D-DE62F4874366@fusesource.com> References: <1351387028399-4658355.post@n4.nabble.com> <8261914C-74DB-4699-B03D-DE62F4874366@fusesource.com> Subject: Re: ActiveMQ Shuts Down ItSelf MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Torsten, Thanks for your response. It's a pretty empty machine and there isn't lot running on that. However, I have asked my system admin to do a check on the OOM killer. Thanks for the pointer. For now, I started the broker in the background mode (nohup ./activemq start &) instead of just (./activemq start) and the broker is up and running for the past 50 hours. I'm not sure it makes any difference as I started the broker using the latter method on the smaller machine. Thanks, Ragu -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Shuts-Down-ItSelf-tp4658355p4658373.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.