Thanks for the clarification.
On Thu, Jul 9, 2020 at 6:11 AM Oleg Kalnichevski wrote:
> On Wed, 2020-07-08 at 14:49 -0400, Evan J wrote:
> > I wanted to clarify whether *MaxPerRoute* is per IP, and not per URL.
> > e.g.
> >
> > http://example.com/api/getData
> &
I wanted to clarify whether *MaxPerRoute* is per IP, and not per URL. e.g.
http://example.com/api/getData
http://example.com/api/getFin
http://example.com/route/notification
http://otherhost.com/api/deposite
Are the first three URLs considered as a single route, and therefore the
MaxPerRoute is
n
>
> so
> 1. logging or posting a full stackrace would make the reason obvious from
> the beginning
> 2.getRootCause() is not always the right thing to do
>
>
> On Wed, Feb 12, 2020 at 5:22 AM Evan J
> wrote:
>
> > On Tue, Feb 11, 2020 at 3:08 PM Alexey Panche
o the target application
> and forward request there.
> While that happens, the client thinks that it already has sent the request
> to the target application and is already waiting for a response.
> In this situation SocketTimeoutException can happen.
>
> On Tue, Feb 11, 2020 at 6:23 PM
can we properly distinguish between these two types of timeouts?
On Tue, Feb 11, 2020, 4:24 AM Oleg Kalnichevski wrote:
> 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)
> >
> >
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). These instances send HTTP requests to a set of gateway
