[
https://issues.apache.org/jira/browse/NIFI-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000622#comment-15000622
]
ASF subversion and git services commented on NIFI-1061:
-------------------------------------------------------
Commit 76690a8ee9ac1907df711525aa2c169168c8c540 in nifi's branch
refs/heads/master from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=76690a8 ]
NIFI-1061 fixed deadlock caused by DBCPConnectionPool.onConfigured()
Current implementation of DBCPConnectionPool was attempting to test if
connection could be obtained via dataSource.getConnection().
Such call is naturally a blocking call and the duration of the block is
dependent on driver implementation. Some drivers (e.g., Phoenix -
https://phoenix.apache.org/installation.html)
attempts numerous retries before failing creating a deadlock when attempt was
made to disable DBCPConnectionPool which was still being enabled.
This fix removes the connection test from DBCPConnectionPool.onConfigured()
operation returning successfully upon creation of DataSource.
For more details see comments in https://issues.apache.org/jira/browse/NIFI-1061
> DBConnectionPool service unable to terminate
> --------------------------------------------
>
> Key: NIFI-1061
> URL: https://issues.apache.org/jira/browse/NIFI-1061
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Randy Gelhausen
> Assignee: Oleg Zhurakousky
> Fix For: 0.4.0
>
> Attachments: Screen Shot 2015-10-23 at 7.17.31 PM.png, nifi-app.log.gz
>
>
> I had a defined flow with an enabled DBConnectionPool using the
> phoenix-client.jar driver. After stopping the NiFi process and restarting it,
> the connection pool is unable to reconnect. Attempting to disable the pool
> never completes the operation. See attached screenshot & nifi-app.log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
