Ok, I understand whtat you mean. Since this is a non-blocking model when we
send the request the thread is released, so I simply have to count the time
passed from I send the response until the 'responseReceived' method is invoked,
and if this time has been exceeded just throw an exception (and
Hi Oleg,
I must admit I do not understand the reason for doing all that in the first
place.
--> It doesn't matter, it's important for B2B integrations in tourism sector,
but that's another story.
I also do not understand what exactly you mean by response timeout. Max
waiting time until a resp
On Fri, 2018-10-19 at 21:07 +0200, Joan Balagueró wrote:
> Hello Oleg,
>
> I think it's a bit more complicated ... Let me explain it:
>
> - we have a pool with a response timeout of 15s
> - this pool is shared by 2 webservices, ws1 and ws2. Ws1 uses the
> pool's response timeout, but ws2 uses its
