Hi Fabio -
If you’re getting a “read timed out,” you may have already gotten past the SSL handshake. That error means you’re waiting to receive data from the server, but no data arrived in time. There’s a “timeout” input variable in the pub.client:http service that you can play with. If you don’t specify a value for that variable, the IS will use the value from watt.net.timeout so you could also configure it there if you prefer to set it globally (see Reverb)
Having said this, in my experience, timeouts are typically due to a more deeply rooted issue, so here are some things you can try to find the root cause:
-
Ensure you’re using the correct URL. I noticed the URL you shared in your post had back-slashes instead of forward-slashes. I’m sure that was a typo, but just in case, make sure the URL is correct.
-
If the server allows it, temporarily change to simple HTTP instead of HTTPS to eliminate TLS as a variable.
-
Try pulling a different file from the server to determine if this problem is specific to the file (e.g. try pulling a small text file).
-
Try pulling the file down via a different mechanism. In other words, from the same server where the IS is running, can you download the file via a browser or via curl?
-
Try pulling the file from a different Integration Server (e.g. one running on your local machine).
-
If the server you’re pulling the file from is behind a load balancer, can you go directly to the server to determine if it’s an issue with the load balancer?
-
Does anything get logged in the target server when you attempt your request?
Trying these different things should help you get closer to determining the root cause of your timeouts.
Hope this helps,
Percio
#Integration-Server-and-ESB#webMethods#Service-Designer