Forums - Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 318 subscribers
  • Views 1382 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 Children
  • 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.
  • 0 in reply to Matt Marum

    Hi Matt,

    Thanks for your reply. 

    The customer had confirmed that they had some network configuration to block SOAPAction Header. They have fixed the configuration to allow SOAPAction header.

    Now, we are facing a new issue with customer SugarCRM SOAP login api.

    When we are passing the following header, the customer Sugarcrm server is unable to read the body of the SOAP login api and giving "error in msg parsing: xml was empty, didn't parse!"

    Transfer-Encoding            chunked

    When we remove this header in the request, the Soap login api request is successful.

    Can you please let me know, if there is any setting in Sugarcrm around the Transfer-Encoding header.

    Thanks in advance for the help.