[
https://issues.apache.org/jira/browse/NIFI-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess resolved NIFI-7424.
--------------------------------
Fix Version/s: 1.13.0
Resolution: Duplicate
Closing as duplicate of NIFI-7503 where the solution was merged for 1.13.0
> PutSQL - Flowfiles stuck in incoming queue due to java.sql.SQLException:
> Can't call commit when autocommit=true
> ---------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-7424
> URL: https://issues.apache.org/jira/browse/NIFI-7424
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Ashish
> Priority: Major
> Labels: putsql
> Fix For: 1.13.0
>
> Attachments: Data Flow.png, Error.png, PutSQL Properties.png,
> nifi-app.log
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For standard processor PutSQL, with property "Database Session AutoCommit"
> set to TRUE, it does not allow the incoming flowfile to move to any of the
> relationships (SUCCESS, FAILURE, RETRY), since it throws the following error -
> PutSQL[id=] Failed to process session due to Failed to commit database
> connection due to java.sql.SQLException: Can't call commit when
> autocommit=true: org.apache.nifi.processor.exception.ProcessException: Failed
> to commit database connection due to java.sql.SQLException: Can't call commit
> when autocommit=true
> "Rollback On Failure" and "Support Fragmented Transactions" are set false
> with "Batch Size" value to 1.
>
> Flowfile Content
> INSERT INTO user_nifi (id, name) VALUES (?, ?)
>
> Flowfile Attributes (relevant)
> sql.args.1.type
> 4
> sql.args.1.value
> 25
> sql.args.2.type
> 12
> sql.args.2.value
> Georgie
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
