rkarthik29 edited a comment on pull request #3887: URL: https://github.com/apache/nifi/pull/3887#issuecomment-711021119
@davyam looks like there is an issue with getConnection(). is it probably timing out???? this is the error log o.a.n.controller.StandardProcessorNode Timed out while waiting for OnScheduled of OracleChangeCapture[id=32c99420-0175-1000-0e97-840ff38cca51] to finish. An attempt is made to cancel the task via Thread.interrupt(). However it does not guarantee that the task will be canceled since the code inside current OnScheduled operation may have been written to ignore interrupts which may result in a runaway thread. This could lead to more issues, eventually requiring NiFi to be restarted. This is usually a bug in the target Processor 'OracleChangeCapture[id=32c99420-0175-1000-0e97-**840ff38cca51]' that needs to be documented, reported and eventually fixed. 2020-10-16 23:40:24,291 ERROR [Timer-Driven Process Thread-1] o.a.n.p.o.c.i.StandardOracleCDCService StandardOracleCDCService[id=32c9c2cd-0175-1000-c663-73fb836e27c7] cannot attach to outbound server: nfxout java.sql.SQLException: Cannot get a connection, general error** 2020-10-16 23:40:24,293 ERROR [Timer-Driven Process Thread-1] o.a.n.p.oraclecdc.OracleChangeCapture OracleChangeCapture[id=32c99420-0175-1000-0e97-840ff38cca51] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: cannot attach to outbound that error seems to come from DBCPConectionPool. Best way to figure out is to run the ITOracleChangeCaptureTest via eclipse,you can then put a breakpoint in standardoraclecdcservice.attach() to get more details on why this is happening. This is probably needs to be handled.. https://issues.apache.org/jira/browse/DBCP-459. You have to investigate why that timeout is happening though. Make sure you are using a thick client for connection to oracle. I don't think that is the cause of this error, but ensure that you are doing that. Karthik ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
