commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DBCP-485) Connection hook functionality
Date Wed, 31 Jan 2018 00:55:00 GMT

    [ https://issues.apache.org/jira/browse/DBCP-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346070#comment-16346070
] 

Phil Steitz commented on DBCP-485:
----------------------------------

Have a look at o.a.c.dbcp2.PoolableConnectionFactory.  There is some minimal logging there
that can be configured for at least your second item.  For the others, see the implementation
of the pool lifecycle methods:  makeObject, validateObject and destroyObject. 

> 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. We are facing
with the problem that there is no Connection Hook in Apache DBCP. Methods what we are using
from BoneCP Connection Hook: onMarkPossiblyBroken, onAcquire, onAcquireFail, onDestroy. Is
there any workaround to how we can get the same functionality with DBCP?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message