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 77A8211FB4 for ; Tue, 6 May 2014 13:27:54 +0000 (UTC) Received: (qmail 45707 invoked by uid 500); 6 May 2014 13:24:45 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 45685 invoked by uid 500); 6 May 2014 13:24:45 -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 45669 invoked by uid 99); 6 May 2014 13:24:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2014 13:24:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.n.gale@gmail.com designates 209.85.214.181 as permitted sender) Received: from [209.85.214.181] (HELO mail-ob0-f181.google.com) (209.85.214.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2014 13:24:39 +0000 Received: by mail-ob0-f181.google.com with SMTP id wm4so3334574obc.12 for ; Tue, 06 May 2014 06:24:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=WtFijptGq8L7ELUh6DGE7mSVyu5nK7vGntxfEluibZ8=; b=IXzHkw5nIR3C4SqvNhP8+Bb4jLY413mbkj9Q8vdFxrK6XLxz9dkhL83uojTw+8B7lE VbD5QkCsFUh+hipvmU3TEhFM/DWDIHD/oTw07+3EzxUjJ928qGLzZi6tQ1+KvvU3xLqm dfqPPD04Pb23HBd8JDHsZhakcTwNhCe9CJv3S6N0JbolEu7EbPtzVAgIqIf3FJ/jI8AV M7E8CQij7tZ/7rhias36ZqfRxaa5npo7yUPkoiDTw7yan8aAkV/0hUVueasMhm9M02lF i7xI19MCEyKaGKxbXSkeWWHDk9adSvfhMpRhGOnmOCqUOx77lBOfKP//2va/T+r9EU5I VTlA== X-Received: by 10.182.42.136 with SMTP id o8mr1346170obl.80.1399382659035; Tue, 06 May 2014 06:24:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.39.135 with HTTP; Tue, 6 May 2014 06:23:48 -0700 (PDT) From: Paul Gale Date: Tue, 6 May 2014 09:23:48 -0400 Message-ID: Subject: Choice of IO exception handler with pluggable storage lockers? To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001a11c305c24bf90a04f8bb2ae9 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c305c24bf90a04f8bb2ae9 Content-Type: text/plain; charset=UTF-8 Hi, ActiveMQ 5.9.1 I have configured ActiveMQ to use the kaha persistence adapter with a lease-database-locker. However, this brings up the question as to which IO exception handler one should configure: the DefaultIOExceptionHandler or the JDBCIOExceptionHandler? The JDBCIOExceptionHandler's method hasLockOwnership() always returns true if the persistence adapter is not an instance of JDBCPersistenceAdapter (which it won't be as I'm using kaha). Therefore it cannot be used. Conversely, the DefaultIOExceptionHandler's hasLockOwnership() method always returns true, therefore it cannot be used to detect when the lease-database-locker loses lock ownership. Is this a bug in the JDBCIOExceptionHandler? Thanks, Paul --001a11c305c24bf90a04f8bb2ae9--