From users-return-50954-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Sun Feb 17 14:32:18 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5FE22180657 for ; Sun, 17 Feb 2019 15:32:18 +0100 (CET) Received: (qmail 44482 invoked by uid 500); 17 Feb 2019 14:32:17 -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 44471 invoked by uid 99); 17 Feb 2019 14:32:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2019 14:32:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4335BC2485 for ; Sun, 17 Feb 2019 14:32:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.896 X-Spam-Level: *** X-Spam-Status: No, score=3.896 tagged_above=-999 required=6.31 tests=[FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.332] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id nl7q5JuLVOft for ; Sun, 17 Feb 2019 14:32:14 +0000 (UTC) Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DB91A62440 for ; Sun, 17 Feb 2019 14:32:13 +0000 (UTC) Received: by mail-wr1-f44.google.com with SMTP id n2so3247890wrw.8 for ; Sun, 17 Feb 2019 06:32:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1VlX4vICi3l5LhQrrP0CLl1CAqVNmCBNO75socJ6xHc=; b=UPoOm8Knp7yZe8ZQnXcfzmxjK4ueChy29++EQSIeA0CgN5hBytjv33MQGw5MydTmSB 3EpDJcStx+rsmakOCFGam/627jRQY8Tq0Pmxu0Z+wgRfsEVkvOAWwbh6KAtKOv9w42V/ 68nfHZK2mB6h9vNu9r4W7WMQyTHiRrbWRH34W5XJTL9giA8wEdojTrPnfYiOqA4elnJ6 b2VE2P4F59aVCZk/H9dAvD/4Vp/5660uli6Gm/wM/BnoHguOPCx0NaTApp+Z6K7PsRwG 3VgGprroqGD1wz/XdqvYHWduKNaMMqi9rcw1YdOfTfjkmgeyhPO7wsfRYjj019R8C3qo PRUA== X-Gm-Message-State: AHQUAuZ0aNvzo7AhvSRFDl6glSn16c7BSJrWQE0j3TXRSn+NEsfOZ0/2 WtlB0DachdfloGC7xLX8LuN1lfkMZkSDyEYVFDe2cQ== X-Google-Smtp-Source: AHgI3IZYlDn8z2xtGhJcB7HHHhSuyopTFI8wV1ttideKTsP/UH1s0qT+XVD0A9ppkXQYqbUmAkbYkA/dIdCXTsHdak8= X-Received: by 2002:adf:e2c8:: with SMTP id d8mr12759206wrj.228.1550413933021; Sun, 17 Feb 2019 06:32:13 -0800 (PST) MIME-Version: 1.0 References: <1444132617560-4702654.post@n4.nabble.com> <1445165772767-4703098.post@n4.nabble.com> <1445248480272-4703112.post@n4.nabble.com> <1446362815368-4703577.post@n4.nabble.com> <1446458959126-4703584.post@n4.nabble.com> <1550169296651-0.post@n4.nabble.com> In-Reply-To: <1550169296651-0.post@n4.nabble.com> From: Tim Bain Date: Sun, 17 Feb 2019 07:32:01 -0700 Message-ID: Subject: Re: JDBC driver with Failover (Master-Slave) MS SQL database To: ActiveMQ Users Content-Type: multipart/alternative; boundary="000000000000bb8f6b058217df19" --000000000000bb8f6b058217df19 Content-Type: text/plain; charset="UTF-8" My last question in that three-year-old thread applies to you too: are you using a wrapper such as Tanuki that would detect the broker process exiting and respond by restarting the ActiveMQ process? This would be the expected way to handle this situation, so if you're not doing that, it's what I'd recommend. Tim On Thu, Feb 14, 2019, 1:58 PM ramapr00 I have the same issue with ActiveMQ. I have two nodes of AMQ and it is > configured to use MS SQL with database cluster. When the database cluster > fails over, my AMQ stops working and I need to re-start it manually to fix > the issue. Could you please post how did you fix your issue? > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html > --000000000000bb8f6b058217df19--