[
https://issues.apache.org/jira/browse/NIFI-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675459#comment-16675459
]
Colin Dean edited comment on NIFI-5789 at 11/5/18 5:31 PM:
-----------------------------------------------------------
This came from my Stack Overflow question, [How can I configure NiFi's
DBCPConnectionPool not to keep idle connections
open?|https://stackoverflow.com/questions/53110163/how-can-i-configure-nifis-dbcpconnectionpool-not-to-keep-idle-connections-open]
was (Author: colindean):
This came from the my Stack Overflow question, [How can I configure NiFi's
DBCPConnectionPool not to keep idle connections
open?|https://stackoverflow.com/questions/53110163/how-can-i-configure-nifis-dbcpconnectionpool-not-to-keep-idle-connections-open]
> DBCPConnectionPool controller service always leaves one connection open
> -----------------------------------------------------------------------
>
> Key: NIFI-5789
> URL: https://issues.apache.org/jira/browse/NIFI-5789
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.8.0
> Environment: Linux, OpenJDK 8, jTDS 1.3.1, MS SQL Server 2016
> Reporter: Colin Dean
> Priority: Major
> Labels: DBCP, database
>
> Out of the box, NiFi (at least, as of 1.8.0), appears to keep open one
> database connection for each DBCPConnectionPool controller service enabled.
> I have multiple DBCPConnectionPool controller services configured to access
> the same server with different options, so this quickly adds up against a
> limited number of connections to my database server. I have a scheduled
> workflow that runs ~nightly. Connections need not be active except when in
> active use during a short window of time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
