Hi Pierre,

I appreciate you taking a look into the issue. I am attaching snapshots of relevant information. One particular aspect is that once the flow is started, I cannot stop ExecuteSQL its processor. I ended up restarting NiFi three times until the flow stopped and I could modify and save properties. That is unusual in my NiFi experience and might be connected to problems with Reliersoft JDBC driver.
From: Pierre Villard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2018 8:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Reliersoft jdbc driver for nifi salesforce integration

Hi Vitaly,

Can you share the configuration of your processor? Can you switch the log level to debug for this processor? Do you have input relationships on the processor (from other processor? failure?)?

Thanks
Pierre

2018-07-10 18:11 GMT+02:00 Vitaly Krivoy <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>:
Has anyone tried to use Reliersoft jdbc driver to pull data from Salesforce using ExecuteSQL processor? I’ve created an object Pricipal__c in Salesforce which contains three records.
I can run “select * from Pricipal__c”  in DbVisualizer and it works as expected. But I get neither data nor errors when I run the same SQL query from ExecuteSQL. The output from the nifi log shows that Reliersoft jdbc driver correctly connects and finds 3 records, but for some reason nothing is placed into flow files. Does anyone have any clues or recommendations? Thanks.
10:33:28,396 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.Driver Connect options: url: jdbc:sforce://login.salesforce.com<http://login.salesforce.com>
2018-07-10 10:33:28,758 INFO [Flow Service Tasks Thread-2] o.a.nifi.controller.StandardFlowService Saved flow controller org.apache.nifi.controller.FlowController@f5ebc9a<mailto:org.apache.nifi.controller.FlowController@f5ebc9a> // Another save pending = false
2018-07-10 10:33:30,361 INFO [Timer-Driven Process Thread-6] rc.Y [78 810458350 1768753242 true true true] Communicating with SF server took 870 ms
2018-07-10 10:33:30,376 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Partner server url: https://na53.salesforce.com/services/Soap/u/35.0/00Df2000001Ga7I
2018-07-10 10:33:30,376 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Partner session Id: 00Df2000001Ga7I!ASAAQDroAcrkJz3eYsqA4Vjzb..V2CoFwQaeMru8Xqg5mZcSdQHaN4kWSp1Czisn1ZSV0hvTQFEdPlwv04kznPOYn58V.E_y
2018-07-10 10:33:33,010 INFO [Timer-Driven Process Thread-6] rc.Y [78 1326156447 1016293809 true true true] Communicating with SF server took 399 ms
2018-07-10 10:33:33,073 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.util.a Metadata is up to date, having last been updated on Fri Jul 06 17:04:06 EDT 2018.
2018-07-10 10:33:33,081 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Disconnecting...
2018-07-10 10:33:33,238 INFO [Timer-Driven Process Thread-6] rc.Y [78 150728874 1016293809 true true true] Communicating with SF server took 126 ms
2018-07-10 10:33:33,238 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Disconnected.
2018-07-10 10:33:33,241 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.Driver Connect options: url: jdbc:sforce://login.salesforce.com<http://login.salesforce.com>
2018-07-10 10:33:34,952 INFO [Timer-Driven Process Thread-6] rc.Y [78 1795241438 -913733887 true true true] Communicating with SF server took 1432 ms
2018-07-10 10:33:34,953 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Partner server url: https://na53.salesforce.com/services/Soap/u/35.0/00Df2000001Ga7I
2018-07-10 10:33:34,953 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Partner session Id: 00Df2000001Ga7I!ASAAQM8pi_NGN4gPpJVZENNgLyy.jbYBza3vrAupKVVeFhBPxCw_VmDifRuHQ2zhUXS1Q5dUavbMyWkMQaItdXrIfAdg3owg
2018-07-10 10:33:37,037 INFO [Timer-Driven Process Thread-6] rc.Y [78 287958716 -1252905073 true true true] Communicating with SF server took 378 ms
2018-07-10 10:33:37,038 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.util.a Metadata is up to date, having last been updated on Fri Jul 06 17:04:06 EDT 2018.
2018-07-10 10:33:37,099 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.p Calling getColumns(null, null, PRICIPAL__C, null) method
2018-07-10 10:33:37,124 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.w No more records to fetch from back-end
2018-07-10 10:33:37,130 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.v PREPARED SELECT TO EXECUTE - select * from Pricipal__c
2018-07-10 10:33:37,132 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.p Calling getColumns(null, null, PRICIPAL__C, null) method
2018-07-10 10:33:37,136 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.w No more records to fetch from back-end
2018-07-10 10:33:37,139 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.v SELECT WITH SET PARAMETERS TO EXECUTE - SELECT Id, OwnerId, IsDeleted, Name, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, LastViewedDate, LastReferencedDate, First_Name__c, Last_Name__c, Email__c FROM Pricipal__c
2018-07-10 10:33:37,139 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.y EXECUTE QUERY FOR SQL - SELECT Id, OwnerId, IsDeleted, Name, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, LastViewedDate, LastReferencedDate, First_Name__c, Last_Name__c, Email__c FROM Pricipal__c USING 32 FETCH THREAD(S)
2018-07-10 10:33:37,167 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.p Calling getColumns(null, null, PRICIPAL__C, null) method
2018-07-10 10:33:37,171 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.w No more records to fetch from back-end
2018-07-10 10:33:37,173 INFO [Timer-Driven Process Thread-6] com.reliersoft.sforce.jdbc.f Elapsed time parse sql query: 7 ms
2018-07-10 10