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 71A914AF7 for ; Mon, 11 Jul 2011 07:54:28 +0000 (UTC) Received: (qmail 49564 invoked by uid 500); 11 Jul 2011 07:54:27 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 48975 invoked by uid 500); 11 Jul 2011 07:54:20 -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 48967 invoked by uid 99); 11 Jul 2011 07:54:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jul 2011 07:54:16 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chubrilo@gmail.com designates 209.85.161.41 as permitted sender) Received: from [209.85.161.41] (HELO mail-fx0-f41.google.com) (209.85.161.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jul 2011 07:54:10 +0000 Received: by fxg9 with SMTP id 9so3390167fxg.28 for ; Mon, 11 Jul 2011 00:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=E6EhYxhbzMVMBwgkcAu8ZmbQ/wdztt3uQwmTfi6fRNs=; b=pM9VOUppUk2hGo8CuVWvksQH4Wie3VP3BHYVnVhD/zDcejOpZ+7+uPoKIMEeZrmx3s ceQT/ggAMnk9hoec8tZdL+uRH+N76dK5QyWLTUqg3lzZUD6+QRr+O5/F/9LXNjjGv+YR Sf7rV3q5LsOgN3fnXqTfNAmA5YV5PNtEz3zHQ= MIME-Version: 1.0 Received: by 10.223.36.89 with SMTP id s25mr7124458fad.9.1310370830264; Mon, 11 Jul 2011 00:53:50 -0700 (PDT) Sender: chubrilo@gmail.com Received: by 10.223.96.8 with HTTP; Mon, 11 Jul 2011 00:53:50 -0700 (PDT) In-Reply-To: <1310143445309-3654613.post@n4.nabble.com> References: <1310143445309-3654613.post@n4.nabble.com> Date: Mon, 11 Jul 2011 09:53:50 +0200 X-Google-Sender-Auth: 7OXgLXybQXfLc364mnJwQtCbRfU Message-ID: Subject: Re: Detecting problems during BrokerService startup From: Dejan Bosanac To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=00151747b362dca9b604a7c67b22 X-Virus-Checked: Checked by ClamAV on apache.org --00151747b362dca9b604a7c67b22 Content-Type: text/plain; charset=ISO-8859-1 Hi, this particular of waiting the lock on the database will not be propagated, as it's a regular scenario for master/slave setups http://activemq.apache.org/shared-file-system-master-slave.html All other exceptions will result in startup failure. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, Jul 8, 2011 at 6:44 PM, alexw87 wrote: > Hi > > I'm starting an embedded Broker using spring, and KahaDBPersistenceAdapter > for persistance. > > This all works fine, but I was hoping to see if there was a way of > detecting > startup errors, say if another instance was started. > > eg : > Database activemq-data\auditBroker\KahaDB\lock is locked... waiting 10 > seconds for the database to be unlocked. > > Is there anyway of bubbling up these exceptions so I can terminate the > application, as currently when using this approach, the executing thread > just sits waiting for the lock to unlock, which it won't > > Any Help or suggestions would be most welcome. > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Detecting-problems-during-BrokerService-startup-tp3654613p3654613.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --00151747b362dca9b604a7c67b22--