function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
JRKarpJRKarp 

Data Loader Connection Exception

Just this Monday we started experience a connection exception with our scheduled command line calls to the data loader.  The data loader will start loading the data but will throw an exception midway through on each upsert job now.  This is happening in 2 out of our 4 environments.  No changes happened on our side....I have used asterisks to mask certain information below in the stack trace.  You can see it connects successfully but in the middle of the job seems to have issues.  Havent changed anything in months, ran perfectly until this past Monday.


F:\Program Files (x86)\salesforce.com\Data Loader\UC4>"../bin/process.bat" "../Configuration" contactUpsert
2014-06-16 03:02:37,876 INFO  [main] controller.Controller initLog (Controller.java:389) - Using built-in logging configuration, no log-conf.xml in F:\Program Files (x86)\salesforce.com\Data Loader\UC4\log-conf.xml
2014-06-16 03:02:37,891 INFO  [main] controller.Controller initLog (Controller.java:391) - The log has been initialized
2014-06-16 03:02:37,891 INFO  [main] process.ProcessConfig getBeanFactory (ProcessConfig.java:103) - Loading process configuration from config file: F:\Program Files (x86)\salesforce.com\Data Loader\UC4\..\Configuration\process-conf.xml
2014-06-16 03:02:38,047 INFO  [main] xml.XmlBeanDefinitionReader loadBeanDefinitions (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from file [F:\Program Files (x86)\salesforce.com\Data Loader\UC4\..\Configuration\process-conf.xml]
2014-06-16 03:02:38,235 INFO  [contactUpsert] controller.Controller initConfig (Controller.java:327) - config dir created at F:\Program Files (x86)\salesforce.com\Data Loader\UC4\..\Configuration
2014-06-16 03:02:39,030 INFO  [contactUpsert] controller.Controller initConfig (Controller.java:355) - The controller config has been initialized
2014-06-16 03:02:39,030 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:116) - Initializing process engine
2014-06-16 03:02:39,030 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:119) - Loading parameters
2014-06-16 03:02:39,030 INFO  [contactUpsert] config.LastRun load (LastRun.java:96) - Last run info will be saved in file: F:\Program Files (x86)\salesforce.com\Data Loader\UC4\..\Configuration\contactUpsert_lastRun.properties
2014-06-16 03:02:39,139 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:127) - Logging in to: https://test.salesforce.com
2014-06-16 03:02:39,155 INFO  [contactUpsert] client.PartnerClient login (PartnerClient.java:478) - Beginning Partner Salesforce login ....
2014-06-16 03:02:39,155 INFO  [contactUpsert] client.ClientBase getConnectorConfig (ClientBase.java:123) - Salesforce login will use proxy host: ********
2014-06-16 03:02:39,186 INFO  [contactUpsert] client.PartnerClient loginInternal (PartnerClient.java:519) - Salesforce login to https://test.salesforce.com/services/Soap/u/28.0 as user *******.com.dev
2014-06-16 03:02:40,216 INFO  [contactUpsert] client.ClientBase getConnectorConfig (ClientBase.java:123) - Salesforce login will use proxy host: squid.td.afg port: 3128
2014-06-16 03:02:40,216 INFO  [contactUpsert] dao.DataAccessObjectFactory getDaoInstance (DataAccessObjectFactory.java:51) - Instantiating data access object: \\************\MDS_CRM_Contact.csv of type: csvRead
2014-06-16 03:02:40,216 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:132) - Checking the data access object connection
2014-06-16 03:02:40,231 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:137) - Setting field types
2014-06-16 03:02:41,261 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:141) - Setting object reference types
2014-06-16 03:02:44,396 INFO  [contactUpsert] process.ProcessRunner run (ProcessRunner.java:145) - Creating Map
2014-06-16 03:02:44,412 INFO  [contactUpsert] action.OperationInfo instantiateAction (OperationInfo.java:95) - Instantiating action for operation: upsert
2014-06-16 03:02:44,459 INFO  [contactUpsert] controller.Controller executeAction (Controller.java:120) - executing operation: upsert
2014-06-16 03:02:44,459 INFO  [contactUpsert] action.AbstractAction execute (AbstractAction.java:120) - Loading: upsert
2014-06-16 03:02:49,654 INFO  [contactUpsert] progress.NihilistProgressAdapter setSubTask (NihilistProgressAdapter.java:78) - Processed 200 of 40,596 total records. Rate: 263,000 records per hour. Estimated time to complete: 9 minutes and 11 seconds.  There are 200 successes and 0 errors.
2014-06-16 03:02:55,129 INFO  [contactUpsert] progress.NihilistProgressAdapter setSubTask (NihilistProgressAdapter.java:78) - Processed 400 of 40,596 total records. Rate: 275,000 records per hour. Estimated time to complete: 8 minutes and 45 seconds.  There are 400 successes and 0 errors.
2014-06-16 03:02:56,752 INFO  [contactUpsert] progress.NihilistProgressAdapter setSubTask (NihilistProgressAdapter.java:78) - Processed 600 of 40,596 total records. Rate: 1,590,000 records per hour. Estimated time to complete: 1 minutes and 30 seconds.  There are 600 successes and 0 errors.
2014-06-16 03:03:57,138 ERROR [contactUpsert] client.PartnerClient runOperation (PartnerClient.java:332) - Error while calling web service operation: upsert, error was: Failed to send request to https://************--Dev.cs11.my.salesforce.com/services/Soap/u/28.0/*************
com.sforce.ws.ConnectionException: Failed to send request to https://**********--Dev.cs11.my.salesforce.com/services/Soap/u/28.0/***********
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:120)
at com.sforce.soap.partner.PartnerConnection.upsert(PartnerConnection.java:1094)
at com.salesforce.dataloader.client.PartnerClient$3.run(PartnerClient.java:100)
at com.salesforce.dataloader.client.PartnerClient$3.run(PartnerClient.java:92)
at com.salesforce.dataloader.client.PartnerClient.runOperation(PartnerClient.java:328)
at com.salesforce.dataloader.client.PartnerClient.loadUpserts(PartnerClient.java:250)
at com.salesforce.dataloader.action.visitor.UpsertVisitor.executeClientAction(UpsertVisitor.java:52)
at com.salesforce.dataloader.action.visitor.PartnerLoadVisitor.loadBatch(PartnerLoadVisitor.java:66)
at com.salesforce.dataloader.action.visitor.DAOLoadVisitor.visit(DAOLoadVisitor.java:105)
at com.salesforce.dataloader.action.AbstractLoadAction.visit(AbstractLoadAction.java:85)
at com.salesforce.dataloader.action.AbstractAction.execute(AbstractAction.java:129)
at com.salesforce.dataloader.controller.Controller.executeAction(Controller.java:121)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:149)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:100)
at com.salesforce.dataloader.process.ProcessRunner.main(ProcessRunner.java:253)
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:628)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.updateSecureConnection(DefaultClientConnectionOperator.java:232)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.layerProtocol(ManagedClientConnectionImpl.java:401)
at org.apache.http.impl.client.DefaultRequestDirector.establishRoute(DefaultRequestDirector.java:837)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:644)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
at com.salesforce.dataloader.client.HttpClientTransport.getContent(HttpClientTransport.java:129)
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:96)
... 14 more
2014-06-16 03:03:57,138 ERROR [contactUpsert] action.AbstractAction handleException (AbstractAction.java:204) - Exception occured during loading
com.salesforce.dataloader.exception.LoadException: Failed to send request to https://*********--Dev.cs11.my.salesforce.com/services/Soap/u/28.0/***********
at com.salesforce.dataloader.action.visitor.DAOLoadVisitor.handleException(DAOLoadVisitor.java:147)
at com.salesforce.dataloader.action.visitor.DAOLoadVisitor.handleException(DAOLoadVisitor.java:151)
at com.salesforce.dataloader.action.visitor.PartnerLoadVisitor.loadBatch(PartnerLoadVisitor.java:70)
at com.salesforce.dataloader.action.visitor.DAOLoadVisitor.visit(DAOLoadVisitor.java:105)
at com.salesforce.dataloader.action.AbstractLoadAction.visit(AbstractLoadAction.java:85)
at com.salesforce.dataloader.action.AbstractAction.execute(AbstractAction.java:129)
at com.salesforce.dataloader.controller.Controller.executeAction(Controller.java:121)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:149)
at com.salesforce.dataloader.process.ProcessRunner.run(ProcessRunner.java:100)
at com.salesforce.dataloader.process.ProcessRunner.main(ProcessRunner.java:253)
Caused by: com.sforce.ws.ConnectionException: Failed to send request to https://*********--Dev.cs11.my.salesforce.com/services/Soap/u/28.0/*************
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:120)
at com.sforce.soap.partner.PartnerConnection.upsert(PartnerConnection.java:1094)
at com.salesforce.dataloader.client.PartnerClient$3.run(PartnerClient.java:100)
at com.salesforce.dataloader.client.PartnerClient$3.run(PartnerClient.java:92)
at com.salesforce.dataloader.client.PartnerClient.runOperation(PartnerClient.java:328)
at com.salesforce.dataloader.client.PartnerClient.loadUpserts(PartnerClient.java:250)
at com.salesforce.dataloader.action.visitor.UpsertVisitor.executeClientAction(UpsertVisitor.java:52)
at com.salesforce.dataloader.action.visitor.PartnerLoadVisitor.loadBatch(PartnerLoadVisitor.java:66)
... 7 more
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:628)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.updateSecureConnection(DefaultClientConnectionOperator.java:232)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.layerProtocol(ManagedClientConnectionImpl.java:401)
at org.apache.http.impl.client.DefaultRequestDirector.establishRoute(DefaultRequestDirector.java:837)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:644)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
at com.salesforce.dataloader.client.HttpClientTransport.getContent(HttpClientTransport.java:129)
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:96)
... 14 more
2014-06-16 03:03:57,138 ERROR [contactUpsert] progress.NihilistProgressAdapter doneError (NihilistProgressAdapter.java:58) - Failed to send request to https://********--Dev.cs11.my.salesforce.com/services/Soap/u/28.0/************
Program 'UC4 Job Messenger' version '9.00A' started

Pravi_1133Pravi_1133
Check your proxy settings again and also firewall restrictions on Dev.cs11.my.salesforce.com/services/Soap/u/28.0.

---Praveen.
JRKarpJRKarp
Proxy settings are good and the proxy has no firewall restrictions.  Its odd as you can see above in the logs in establishes a connection and uploads a good amount of data before it bombs.
Pravi_1133Pravi_1133
Hey, Someone got similar problem ad they turned-off the bulk API and their problem got fixed. have you tried that?

--Praveen
JRKarpJRKarp
Not using the bulk API for this job
JHarkJHark
I received the same error message when updating over 22K records via the Apex Data Loader. I could login and start the job, but it would error out with the same message after loading "x" number of records. I broke up the job into files with less than 10K records each and was then successful. Hope this helps.
jpgilbertjpgilbert
I'm also having this issue of the job erroring after 2000+ records. So part of the data is loaded without issue and then it errors out saying "Failed to send request to https://xxxxx.my.salesforce.com/services/Soap/u/29.0/00DG000000hoBs"

Bulk is not turned on and we don't use a proxy for HTTPS.
JRKarpJRKarp
Never was able to resolve this as I was only batching 200 records at a time.  However, it did go away on its own... I am assuming they tightened up their API during one of the releases.
Todd ScheidererTodd Scheiderer

I am having this same problem as of Monday this week.  Was there ever a proper solution found to fix this error.  Most of my data executes fine and then the error "Failes to send request to https:........"  pops up and batch process ends.    

Help.
Chris Zacny 3Chris Zacny 3
We are seeing this issue as well as of 9.21.16, similar to Chad. Everything has been working fine up until now; this appeared to pop up out of nowhere.
Todd ScheidererTodd Scheiderer
Chris,  I have moved all of my batch files to a different Proxy that the previous set up.   Still no anwer on the issue or cause of failure.  However the new proxy seems to be allowing full batch processing today.  I am reingaging dialy automation without Pauses today and testing to see if this holds true on automatic batch files.    Fingers Crossed.
Jason DavisJason Davis
I've had this same issue off and on.  I'm thinking it is something in our infrastructure (firewall, proxy, etc).  Will repost if I find a solution.