on ‎2016 Jul 07 2:26 AM
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
Request clarification before answering.
Try running the OData service URL independently in the browser and see if it works.
BR.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
| User | Count |
|---|---|
| 12 | |
| 9 | |
| 7 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.