Having the SOAP blues today?

bsoremsugar —  January 24, 2011 — 4 Comments

We’ve noticed internally that requests to the xmlsoap.org domain seem to be rather slow today ( a quick test to http://schemas.xmlsoap.org/soap/encoding/ is taking 30 seconds to respond as I write this post ). This has impact on anyone using SOAP web services, especially those from SugarCRM instances, as pulling in the WSDL file is taking much longer than normal.

There’s a few different ways to help this situation out

  1. Make sure your SOAP client is caching the WSDL file. Since the WSDL file for you Sugar instance doesn’t change, set this to a pretty high number ( the PHP SoapClient defaults to 24 hours ). This will make it so that you’ll only take one hit for the slowness, and afterwards the WSDL file will be read instantly from cache. The PHP SoapClient has WSDL caching on by default; if you are using NuSOAP, check out this blog post for a quick howto.
  2. Use your SOAP client in non-WSDL mode. The downside of this is if your SOAP client let’s you call the remote methods as if they were native ( for example, calling $soapClient->login($user_auth) to login to your Sugar instance instead  of $soapClient->__soapCall(‘login’,array($user_auth)) ) you’ll have to revert back to the direct method of calling them using the call method of your SOAP client. This may or may not be a big deal for depending upon how you have wrote your SOAP code.

And if you are looking for an even bigger speedup, move to using the REST web services interface introduced in Sugar 5.5 for much higher performance.

4 responses to Having the SOAP blues today?

  1. 

    schemas.xmlsoap.org/soap/encoding/ is answering “You do not have permission to view this directory or page.” today.

    What is happening ???
    I pulled the contents of that page from google cache and made a bypass on schema.xmlsoap.org to my own webserver to spit the content out. Works for me now.

  2. 

    API is not working at all today. I’m getting the same error as Bjorn. I really don’t want to have to do what Bjorn had to do. Are you guys working on this?

  3. 

    I’m afraid someone has sabotaged this by purpous. The server “schemas.xmlsoap.org” is owned by Microsoft, it seems it is made slow or unaccessible for some reason. This must be a world wide problem of a big magnitude.
    I think all “dynamic” soap clients (like the native one in PHP5) or maybe nusoap as well will have a problem.
    I noticed that if the wsdl cache file is still present in the /tmp (or similar) directory, the web service was still working.
    This has nothing to do with WordPress but is a problem that affects SOAP. Most webservices only need this access during build time, but PHP is more dynamic and accesses more often(once an hour or so)

Trackbacks and Pingbacks:

  1. SOAP Login authentication causes HTTP 500 - SugarCRM Forums - November 28, 2011

    […] […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s