From issues-return-66218-archive-asf-public=cust-asf.ponee.io@commons.apache.org Wed Jan 31 01:55:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 8037318061A for ; Wed, 31 Jan 2018 01:55:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6FEC2160C54; Wed, 31 Jan 2018 00:55:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B87CA160C53 for ; Wed, 31 Jan 2018 01:55:03 +0100 (CET) Received: (qmail 51372 invoked by uid 500); 31 Jan 2018 00:55:02 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 51359 invoked by uid 99); 31 Jan 2018 00:55:02 -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; Wed, 31 Jan 2018 00:55:02 +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 6885CC03A7 for ; Wed, 31 Jan 2018 00:55:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] 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 eOirxyxjWWZz for ; Wed, 31 Jan 2018 00:55:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 18CDA5FB5E for ; Wed, 31 Jan 2018 00:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4FD01E0115 for ; Wed, 31 Jan 2018 00:55:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 090D221301 for ; Wed, 31 Jan 2018 00:55:00 +0000 (UTC) Date: Wed, 31 Jan 2018 00:55:00 +0000 (UTC) From: "Phil Steitz (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DBCP-485) Connection hook functionality MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DBCP-485?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D163460= 70#comment-16346070 ]=20 Phil Steitz commented on DBCP-485: ---------------------------------- Have a look at o.a.c.dbcp2.PoolableConnectionFactory.=C2=A0 There is some m= inimal logging there that can be configured for at least your second item.= =C2=A0 For the others, see the implementation of the pool lifecycle methods= :=C2=A0 makeObject, validateObject and destroyObject.=C2=A0 > Connection hook functionality > ----------------------------- > > Key: DBCP-485 > URL: https://issues.apache.org/jira/browse/DBCP-485 > Project: Commons Dbcp > Issue Type: Wish > Affects Versions: 2.2.0 > Reporter: Tamas Lokucza > Priority: Minor > > We would like to change our connection pool from BoneCP to Apache DBCP. W= e are facing with the problem that there is no Connection Hook in Apache DB= CP. Methods what we are using from BoneCP Connection Hook: onMarkPossiblyBr= oken, onAcquire, onAcquireFail, onDestroy. Is there any workaround to how w= e can get the same functionality with DBCP? -- This message was sent by Atlassian JIRA (v7.6.3#76005)