ent.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
>
> Regards,
> Petr
>
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, August 24, 2017 10:04 AM
> To: Tomcat Users List
> Subject: Re: Tomcat 8.5.15/
only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Regards,
Petr
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Thursday, August 24, 2017 10:04 AM
To: Tomcat Users List
Subject: Re: Tomcat 8.5.15/502: Bad Gateway
On 24/08/17 0
On 24/08/17 08:39, Petr Nemecek wrote:
> Hello,
>
> I have a Tomcat behind IIS, and I get the 502: Bad Gateway error for long
> running requests.
>
> After some experiments I've found out, that if I use connector 8082 (see
> below), I have this problem, but when I switch to 8084 (see below), th
Hello,
I have a Tomcat behind IIS, and I get the 502: Bad Gateway error for long
running requests.
After some experiments I've found out, that if I use connector 8082 (see
below), I have this problem, but when I switch to 8084 (see below), the problem
disappears. The only difference is that pr
