Forums - Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 318 subscribers
  • Views 1380 views
  • Users 0 members are here
Forum Actions
Related

SugarCRM soap apis giving read time out

test test

We have one customer who is on SugarCRM on premise 8.0.2 version. When we are trying to access SugarCRM instance of this customer via SOAP apis, we are getting read timeout exception. I have looked through the SugarCRM release notes and found that there was one issue related to SOAP apsi which was fixed in 8.0.1 and 8.1.0.

  • 80813 : The SOAP API and is not available for use, rendering applications which use SOAP unable to connect to Sugar. 

Can someone please confirm if the fix is available in 8.0.2 or the issue was introduced again in 8.0.2?

Parents Reply
  • 0 in reply to Matt Marum

    Hi Matt,

    Thanks for the reply.

    I am trying to hit login soap api via postman to the customer SugarCRM on premise (8.0.2) instance. 

    URL: {site_url}/soap.php

    Method:POST

    Headers: 

    Content-Type - text/xml; charset=UTF-8
    Host - {hostname}
    SOAPAction - "urn:login"
    request body:
    xml request for login soap api.
    This request is failing with read time out.
    When I remove SOAPAction header from the request. I am able to get response from customer SugarCRM instance.
    Sending SOAPAction with empty value is also giving me read timeout.
    I tried on other SugarCRM cloud instance of 8.2.0. The soap api request is working fine with both SOAPAction header and without SOAPAction header.
    Do you have any idea, what can be the issue here for getting read time out when we are passing SOAPAction header.
    Thanks in advance for the help.
Children
  • 0 in reply to test test

    I'm not sure why this would fail. It seems like the login action is timing out for some reason. You can check PHP error log and the sugarcrm.log file to see if there's anything in those that points to a problem.

    Also, you can see if you can reproduce this problem with a stock (brand new) instance of Sugar 8.0.2. If it works in a stock version of Sugar but not in the customer's instance then you know it has something to do with the customer's environment (for example, maybe a customization is getting in the way.)

    App Ecosystem @ SugarCRM