On Tue, Feb 11, 2020 at 3:08 PM Alexey Panchenko
wrote:
> I guess, It can depends on which level load balancer operates.
> if load balancer is layer 4 (TCP) then for the operating system it looks
> like connection is made directly to the target application. In this case
> exception should happen
I guess, It can depends on which level load balancer operates.
if load balancer is layer 4 (TCP) then for the operating system it looks
like connection is made directly to the target application. In this case
exception should happen during connect and be wrapped as
ConnectTimeoutException
but if
Thank you for your response.
I'm trying to understand your statement. Are you saying when connection
times out, SocketTimeoutException is thrown, and then the library captures
it and rethrows ConnectTimeoutException?
Bottom line, first, is what I explained the expected behavior, and second,
how
On Mon, 2020-02-10 at 23:25 -0500, Evan J wrote:
> Hi,
>
> (looks like I'd sent this to a wrong user group originally)
>
> We deploy an application B (which is basically a backend application
> serving a web application) to a cluster of application servers (JBoss
> EAP
> 7.2 -- 8 instances).
