Hi,
From prod dataminer, I am not able to call http service and getting timeout error popup but same connector with same device is working fine on stg dataminer.
Note: this is http service. It is not https.
Stream Log:
<- 09:55:40 - GET http://10.xx.xx.xx:80/api/deviceinfo
-> 09:55:40 - Error : 12030. [ERROR_WINHTTP_CONNECTION_ERROR]
-> 09:55:40 - Get for HttpResponseBody_deviceinfo had error : Error : 12030. [ERROR_WINHTTP_CONNECTION_ERROR]
stg:
Server version : 10.4.0.0-15646
prod with cassandra database:
Server version : 10.4.0.0-15230
From powershell, I am able to do below on both servers and response is coming in less than second:
Invoke-WebRequest http://10.xx.xx.xx:80/api/deviceinfo
From IE browser I am able to browse below URL and 'http://10.xx.xx.xx' is added as trusted site:
http://10.xx.xx.xx:80/api/deviceinfo
Any suggestions?
Thank you!
Based on the symptoms you're describing, it seems likely that there is a difference in the proxy configuration between the production and staging server.
To troubleshoot this step by step, the first thing to verify is whether the DataMiner production server is expected to route its HTTP traffic through a proxy.
If you're certain that it shouldn't, you can try adding the bypassproxy keyword to the bus address of the HTTP connection. This will instruct the system to bypass any proxy settings configured at the WinHTTP level.
What value is currently configured for the 'Timeout of a single command (ms)' property in the HTTP connection, and would increasing it significantly be worth trying as a test?
It is 6000. We increase this also but no luck.
Have you already checked at the network level using a packet sniffer like Wireshark to better understand what’s happening? If you'd like, feel free to forward the data to support.data-acquisition@skyline.be, and we’ll be happy to assist you further with the troubleshooting.
As mentioned before, with powershell and browser it is working and response is coming in less than sec.
Network team rechecked and confirmed that there is not connectivity or packet loss issue.
Still timing out even adding the bypassproxy