Question Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost)) in Technology Q&A

HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Former Member — Thu, 07 Jul 2016 01:26:55 GMT

Sorry guys, I'm pretty new to this stuff but was hoping to get an answer on the following error ...

HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Everything appears to be in place but still no luck.

I've added property ClientReadTimeout to the destination with value 300000 but all it does is take longer to arrive at the above error.

If I look at the logs on cloud connector, there is some activity ...

2016-07-07 10:35:00, Allowing access for user dixonb to resource /sap/opu/odata/sap/y_companycode_list_srv/ on system ecd:443

2016-07-07 11:05:37, Allowing access for user dixonb to resource /sap/opu/odata/SAP/Y_COMPANYCODE_LIST_SRV/ on system ecd:443

2016-07-07 11:05:56, Allowing access for user dixonb to resource /sap/opu/odata/SAP/Y_COMPANYCODE_LIST_SRV/ on system ecd:443

2016-07-07 11:09:59, Allowing access for user dixonb to resource /sap/opu/odata/SAP/Y_COMPANYCODE_LIST_SRV/ on system ecd:443

This is my neo-app.json file ...

{

"welcomeFile": "/webapp/index.html",

"routes": [

{

"path": "/resources",

"target": {

"type": "service",

"name": "sapui5",

"entryPath": "/resources"

"description": "SAPUI5 Resources"

{

"path": "/test-resources",

"target": {

"type": "service",

"name": "sapui5",

"entryPath": "/test-resources"

"description": "SAPUI5 Test Resources"

{

"path": "/destinations/ECD020",

"target": {

"type": "destination",

"name": "ECD020"

"description": "ECD020"

}

"sendWelcomeFileRedirect": true

}

... and this is the entry in my manifest.json ...

If I try to add the OData service using New-->OData Service I get the same outcome ...

So it's trying very hard but not getting through.

Any help would be much appreciated.

Thanks

Brad

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Ankit_Maskara — Thu, 07 Jul 2016 04:10:59 GMT

Try running the OData service URL independently in the browser and see if it works.

BR.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Former Member — Thu, 07 Jul 2016 04:21:00 GMT

Yeah, already done that with no issues. It's the first thing I developed. Thanks for the thought though.

Further to that, when I try to add the OData service through the wizard, again, I see entries in the audit log on cloud connector but for the service collection OData service delivered by SAP ...

2016-07-07 14:40:46, Allowing access for user dixonb to resource /sap/opu/odata/IWFND/CATALOGSERVICE/ServiceCollection on system ecd:443

... so again, it's trying hard but it's not specific to my custom service.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Ankit_Maskara — Thu, 07 Jul 2016 07:02:37 GMT

Sorry this seems more of infrastructure issue then the application issue and i would not be able to help.

Let's wait for other gurus.

BR.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Former Member — Mon, 11 Jul 2016 01:47:13 GMT

For those interested, there has been some progress on this.

Working with a colleague, we re-routed cloud connector to bypass the web dispatcher. This has actually meant that I can view all services available within the ECC system.

It doesn't solve the issue but we're working with basis to understand what might be causing it.

I'll update if and when I do have the specific details.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

fabianaguimar — Fri, 31 May 2019 17:34:07 GMT

I have the same issue and i had hope to fix it... Someone can help?

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

former_member615642 — Mon, 05 Aug 2019 09:43:18 GMT

I am also facing same issue I have tried separate in browser it is not working and When i try same in sap gateway its is working fine. Could you please suggest how your issue has resolved.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

Ankit_Maskara — Mon, 05 Aug 2019 15:48:18 GMT

Hi Amita,

As mentioned by me, it's an infrastructure issue and I cannot help. Please open a new thread and wait for other gurus.

BR.

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

former_member604168 — Wed, 22 Apr 2020 16:40:52 GMT

Did anyone resolve this issue ? I am facing the same .

Re: HTTP Status 504 - Socket connection timed out for host https://ecd:443. Reason: Read timed out (local port 45205 to address 127.0.0.1 (localhost), remote port 20001 to address 127.0.0.1 (localhost))

harald_bucher_linde — Mon, 10 Jul 2023 14:47:34 GMT

I had the same issue and found the note 3252830:

Resolution

In your BTP destination the property "HTML5.SocketReadTimeoutInSeconds" must be added and set to the value of the property to 300 seconds.

This solved the timeout error for me.