Skip to main content
Published: July 29 2005, 12:00:00 AMUpdated: November 28 2020, 1:28:40 PM

I am using the SOAP API and I am getting the following error:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:HTTP</faultcode><faultstring>(0)null</faultstring><detail><string>return code: 0
</string><ns2:HttpErrorCode xmlns:ns2="http://xml.apache.org/axis/">0</ns2:HttpErrorCode></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

or I am using the Java SDK and I am getting the following exception:
com.ebay.sdk.SdkSoapException: (0)null

What is going on? Is there anything I can do to resolve this problem?

The problem here is that the amount of time the API call is taking to process on eBay servers is greater than the 2 minute timeout that our network architecture enforces on the front end. This 2 minute timeout applies to all API calls wether it's through SOAP or Schema XML ... and it has been in place for several years.

When the 2 minute processing limit is reached the call will return with the behavior you are seeing in the SOAP call or the Java SDK call that you are making (different technologies will see different behaviors when the 2 minute limit is reached, but the net effect is that the call returns with no data).

This generally happens on calls such as  GetAccount or GetSellerEvents because depending on the input they can result in a large data set ... which is almost always the root cause of the problem.
Therefore if you do get this result, please take a look at how you are making the API call. If you are requesting data over a large period of time which can be done in  GetSellerEvents or GetAccount, then please break up the single call into several calls with each call covering a smaller time frame. In this way you can get the data for the entire period of time in multiple calls instead of having the single call which times out everytime.

How well did this answer your question?
Answers others found helpful