function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
dotnetericdotneteric 

connection was cancelled here - Sporadic Error While Calling Apex Service

We have an automated process that loads data from CSV files into SF via the web services API.  The data is updated and sharing records are created for the data via an Apex Service that we wrote.  We are processing tens of thousands of rows of data, so we call the Apex Service multiple times with a pointer passed to the method letting it know where the last call left off.  This process runs daily and has been in production for 3 months.  Every so often, we receive a soap error that says "connection was cancelled here".  The process terminates when it reaches an error, so we've rerun the process in the past, and it's always worked on the second run.  Unfortunately, we ran it 3 additional times yesterday after the initial failure, and it fails with the same error before the process finishes. 


Has anyone ever seen this error before - "connection was cancelled here"?  A google search of that phrase with quotes around it returns SF related results from the community and a forum, but no solid answer as to the cause or fix of the error.  We've engaged salesforce support, but have gotten nowhere fast. 


The data that gets loaded is for an HR app, so it is critical that we resolve this issue asap.  Any help is greatly appreciated.


Below are log entries for the request and response from our BEA ALSB from which the calls are made (this is only the body of the message):

 

####<Apr 1, 2010 3:31:58 AM EDT> <Info> <ALSB Logging> <crplivesb02> <ALSB_MS05> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1270107118299> <000000> < [PipelinePairNode11, PipelinePairNode11_request, Request Transformation, REQUEST] ====== Authentication granted. Sending Update Employee Shares Link request to SFDC. ========: <soapenv:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://soap.sforce.com/schemas/class/mafDataload">
  <createEmployeeShares>
    <pointerId>014802</pointerId>
  </createEmployeeShares>
</soapenv:Body>>


####<Apr 1, 2010 3:34:01 AM EDT> <Info> <ALSB Logging> <crplivesb02> <ALSB_MS05> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1270107241252> <000000> < [RouteNode10, null, null, ERROR] ========= Received exception while routing to SFDC =============: <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>connection was cancelled here</faultstring>
  </soapenv:Fault>
</soapenv:Body>>


Thanks,

Eric

b-v-bb-v-b

Hello Eric,

 

has you solved this problem? What was the solution?

 

Thanks

Bernhard

nwbienwbie

Hi,

 

Are you facing the issue again? What was the root cause and resolution?

 

Thanks in advance

dotnetericdotneteric

Sorry for not replying sooner.  It seems the error went away after support issued a "physical delete" of the deleted records.  Some background:

 

With time, our recycle bin got up to about 25 million records.  We have a process that empties the recycle bin in addition to deleting the records, but that's still different from the "physical delete" that only SFDC can do.  They said the "sweeper" that actually empties the recycle bin couldn't keep up with the number of records that were being deleted.  Hope this helps you.

 

-Eric