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 5DF58ED91 for ; Thu, 14 Feb 2013 16:30:56 +0000 (UTC) Received: (qmail 40617 invoked by uid 500); 14 Feb 2013 16:30:55 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 40591 invoked by uid 500); 14 Feb 2013 16:30:55 -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 40579 invoked by uid 99); 14 Feb 2013 16:30:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 16:30:55 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 16:30:50 +0000 Received: by mail-ia0-f169.google.com with SMTP id j5so2458153iaf.28 for ; Thu, 14 Feb 2013 08:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=GCpKjSsnTaTQkHpbr5BtkdgHPGUzrC+rVCI+3ODAA1c=; b=WjQ+AvqljD+gVYY1wEwLFbUoNiXKMQOSThdfx2SiuVg5Kp+InGHjB4BxcazowUb6Gb XRndBpWZcnNmXtv/RbV8N5zwMoyq2K/VHcTS1QH6XNwFNNovUeIpwIKtmTKMS/Ypqx5x XhJMTNHID2Ul0AlNtgL9huFt/pTc0ngwOgp4Gel+BZL5+wVGmcTV79y0mqEbwsaT1AfN Li3NXT+syj2AQMe1WAZ06HIYojNrizHUgb2/5v2MWajTOjTeBXDSfqYCGQOVM7G+CqtC qGauanz0UxykS6HtiMjXpliUTDsNvpTYTA02fyzYiaCJCMlK8A5U10L4MqjgTxRcyq2p iZxQ== MIME-Version: 1.0 X-Received: by 10.50.13.208 with SMTP id j16mr122854igc.73.1360859430050; Thu, 14 Feb 2013 08:30:30 -0800 (PST) Received: by 10.50.41.100 with HTTP; Thu, 14 Feb 2013 08:30:29 -0800 (PST) In-Reply-To: <1360858957731-4663430.post@n4.nabble.com> References: <1360858957731-4663430.post@n4.nabble.com> Date: Thu, 14 Feb 2013 09:30:29 -0700 Message-ID: Subject: Re: How to get niotified when broker service stops From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=f46d0447f094eada8f04d5b1c664 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0447f094eada8f04d5b1c664 Content-Type: text/plain; charset=ISO-8859-1 you could register a custom broker plugin and implement the stop() method to notify you in some way. if you use some monitoring tools like nagios you could create an alert. On Thu, Feb 14, 2013 at 9:22 AM, mikmela wrote: > There is a situation when JDBC persistence adapter simply stops the broker > service. This is happening when database locker's keepAlive check fails > due to some database issues... What would be the best way to get notified > about it... In other words, is any way to register a an observer object? or > may be there are other ways? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-get-niotified-when-broker-service-stops-tp4663430.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --f46d0447f094eada8f04d5b1c664--