Api Management not perfoming on SOAP to REST

Question

I have imported the WSDL to the api in API Management portal. The operations are succefully imported, and the rest methods are created as expected. However, when I tried to test one of the method Add it gave an error in tracer mentioning forward-request (21,011.212 ms)
{
"messages": [
"Unable to connect to the remote server",
"Error occured while calling backend service.",
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 45.40.165.23:80"

When I tested the converted body in postman it worked fine, seems some conversion issue with API Management. The web url used for SOAP is http://www.dneonline.com/calculator.asmx

Answer 1

Hi @Manish Nautiyal

Apology for the delay as I was discussing the repro with my team. I was able to repro the issue and looking into traces I can see that APIM is not getting any response from the backend service and timing out exactly at the 21 sec for every request. If I pass the same request that APIM is passing to the backend service http://www.dneonline.com/calculator.asmx then it works and the backend response correctly. This needs to troubleshoot from the backend service why it is not responding to the APIM request. I have tried to deploy my own services and verify that APIM is working as expected.

Trace

 {  
            "source":"forward-request",  
            "timestamp":"2020-11-05T06:51:24.0659887Z",  
            "elapsed":"00:00:21.0275199",  
            "data":{  
               "messages":[  
                  "Unable to connect to the remote server",  
                  "Error occured while calling backend service.",  
                  "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 45.40.165.23:80"  
               ]  
            }  
         }  
  

Answer 2

Hi @MayankBargali-MSFT , I am having the same issue. I have 3 copies of backend service (Dev, UAT and Prod), while the Production backend service is working as expected the UAT and DEV both are failing with the same error. Any idea why my Dev and UAT would start throwing these errors (there has been no change to the backend service)?

forward-request (21,043.937 ms)
{
"messages": [
"Unable to connect to the remote server",
"Error occured while calling backend service.",
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xxx.xxx:80"
]
}

Answer 3

I'm having this exact issue. A backend service isn't reachable by API Management, but is reachable by a VM connected to the same VNET. All calls keep saying "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <ip address>".