[
https://issues.apache.org/jira/browse/NIFI-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980592#comment-14980592
]
Oleg Zhurakousky commented on NIFI-1061:
----------------------------------------
Randy
I'll have a look at it, but here is what I see now. . .
There is some ZooKeeper problem (that is where things start to go south) that
leads to runtime exception that may be misshandled by the NiFi (see
org.apache.nifi.dbcp.DriverShim.connect(..)). This one is what IMHO is the bug
in NiFi. In other words the failures of the target system should not affect the
lifecycle of the service (e.g., ability of being stopped/disabled etc.). Just
wan to make sure that by fixing this bug you may still have a problem with your
connection due to wherever is happening with ZooKeeper.
> 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
> 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)
