[
https://issues.apache.org/jira/browse/NIFI-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122736#comment-16122736
]
Peter Wicks commented on NIFI-4279:
-----------------------------------
Usually when I see this error it's not because of the processor but because of
the DBCP Connection Pool losing a connection but not recognizing it. It then
hands a closed connection to the processor and an error like this sometimes
gets closed (also I've seen 'Closed Pipe').
This may not be your issue, but to check you could try adding a Validation
Query to your Oracle connection if you don't already have one.
> PutDataBaseRecord steam has already been closed
> -----------------------------------------------
>
> Key: NIFI-4279
> URL: https://issues.apache.org/jira/browse/NIFI-4279
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.3.0
> Environment: we have used nifi on openshift cluster and standalone on
> a linux machine.
> Oracle database with version 11.2.0.2
> linux with rhel 7.0
> Reporter: simon water
> Priority: Minor
> Labels: database, nifi, patch, processor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> we have created a table in an Oracle Database with a default sysdate column.
> when i restarted the processor it started throwing the stream has already
> been closed exception
> i have used a csv file with the headers inside of it
> csv Reader that reads the column names from the csv
> the data base version is 11.2.0 Oracle database
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
