You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2018/11/12 18:43:00 UTC

[jira] [Resolved] (NIFI-5790) DBCPConnectionPool configuration should expose underlying connection idle and eviction configuration

     [ https://issues.apache.org/jira/browse/NIFI-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-5790.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

> DBCPConnectionPool configuration should expose underlying connection idle and eviction configuration
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5790
>                 URL: https://issues.apache.org/jira/browse/NIFI-5790
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.8.0
>            Reporter: Colin Dean
>            Priority: Major
>              Labels: DBCP, database
>             Fix For: 1.9.0
>
>
> While investigating a fix for NIFI-5789, I noticed in the [DBCPConnectionPool documentation|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.8.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html] that NiFi appears _not_ to have controller service configuration options associated with [Apache Commons-DBCP|https://commons.apache.org/proper/commons-dbcp/configuration.html] {{BasicDataSource}} parameters like {{minIdle}} and {{maxIdle}}, which I think should be both set to 0 in my particular use case. 
> Alternatively, I think I could set {{maxConnLifetimeMillis}} to something even in the minutes range and satisfy my use case (a connection need not be released _immediately_ but within a reasonable period of time), but this option is also not available.



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