Good evening,
I found a particular problem : I use http_string to send a json file (structured inside as an array of an object) to an external web services.
If I launch in interactive mode ... all function. If I launch in batch mode I receive the errore "Socket has been shut down" when the external process use more than 30 seconds to complete. But the external process in reality close without errors.
This is more strange due the fact that timeout HTTPAPI default is setted to 60 seconds. Besides I set it to 300 seconds (http_setOption('timeout': 300)), but nothing change.
If I send a number of elements in the array that permit to close the remote job within 30 seconds all functions.
So I don't have idea where look at the problem.
The web services that I call stay in a Boomi platform, that in turn call the final web service that stay in a PLM environment (Kubix Link).
The Boomi platform have a timeout default of 2 minutes. And here all is ok.
Thanks a lot
Nalesso Antonio
Use of http_string in batch
-
- Site Admin
- Posts: 872
- Joined: Sun Jul 04, 2021 5:12 am
Re: Use of http_string in batch
Hello,
I have not heard of any difference between interactive and batch.
Much of your message is related to timeout settings. You say you changed it to 300 seconds, and also mentioned "Boomi" had a timeout of 2 minutes. Can you explain how this relates to the problem? I do not understand why you are changing the timeout values.
Can you tell me which version of HTTPAPI you are using? There were changes made to the operating system's TLS/SSL support in 7.3 and 7.4 that required updates to HTTPAPI. If you don't have these updates, they may be causing the problems you are seeing. What version of HTTPAPI are you using?
Aside from that, "socket has been shut down" means that the server has indicated that it will not send any more data over the network connection. This is not related to a timeout.
I have not heard of any difference between interactive and batch.
Much of your message is related to timeout settings. You say you changed it to 300 seconds, and also mentioned "Boomi" had a timeout of 2 minutes. Can you explain how this relates to the problem? I do not understand why you are changing the timeout values.
Can you tell me which version of HTTPAPI you are using? There were changes made to the operating system's TLS/SSL support in 7.3 and 7.4 that required updates to HTTPAPI. If you don't have these updates, they may be causing the problems you are seeing. What version of HTTPAPI are you using?
Aside from that, "socket has been shut down" means that the server has indicated that it will not send any more data over the network connection. This is not related to a timeout.
Re: Use of http_string in batch
Hi Mr. Scott,
thanks for the immediate reply.
In my ignorance I associate the problem "socket has been shut down" with the fact that connection was close after a certain amount of time for it doesn't received any data. For I don't understand any other reason to close the connection. So I focused to timeout period.
Sorry for the missing info. We still use V7R2. I tried both httpapi version 1.42 both 1.45.
The big mystery is why in interactive all it function.
Best regards
Nalesso Antonio
thanks for the immediate reply.
In my ignorance I associate the problem "socket has been shut down" with the fact that connection was close after a certain amount of time for it doesn't received any data. For I don't understand any other reason to close the connection. So I focused to timeout period.
Sorry for the missing info. We still use V7R2. I tried both httpapi version 1.42 both 1.45.
The big mystery is why in interactive all it function.
Best regards
Nalesso Antonio