[
https://issues.apache.org/jira/browse/NIFI-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002155#comment-15002155
]
Bryan Bende commented on NIFI-1153:
-----------------------------------
Should we remove "routing to failure" from the log message when no FlowFile is
present? since there isn't anything being routed failure.
Otherwise, the patch applies and looks good, I'm a +1.
> ExecuteSQL logs errors about FlowFileHandlingException
> ------------------------------------------------------
>
> Key: NIFI-1153
> URL: https://issues.apache.org/jira/browse/NIFI-1153
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments:
> 0001-NIFI-1153-If-no-incoming-FlowFile-don-t-try-to-trans.patch
>
>
> If ExecuteSQL is configured with no incoming connections and is unable to
> obtain a connection to the database via the controller service, it creates a
> lot of less messages of the form:
> 2015-11-11 11:36:43,885 ERROR [Timer-Driven Process Thread-9]
> o.a.nifi.processors.standard.ExecuteSQL
> ExecuteSQL[id=f6563742-585a-4109-91c9-613deca6bd8a] Failed to process session
> due to org.apache.nifi.processor.exception.FlowFileHandlingException: null is
> not known in this session (StandardProcessSession[id=84]):
> org.apache.nifi.processor.exception.FlowFileHandlingException: null is not
> known in this session (StandardProcessSession[id=84])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
