Am 23.03.2018 um 11:19 schrieb Martin Knoblauch:
Hi Rainer,
so basically I took the Apache path and ended up with the following brute
force method:
RewriteCond "%{REQUEST_METHOD}" "GET"
RewriteRule ^/xxx/facelets/logon.xhtml$ - [E=login_jsid:%{HTTP_COOKIE}]
CustomLog
Hi Rainer,
so basically I took the Apache path and ended up with the following brute
force method:
RewriteCond "%{REQUEST_METHOD}" "GET"
RewriteRule ^/xxx/facelets/logon.xhtml$ - [E=login_jsid:%{HTTP_COOKIE}]
CustomLog "/opt/xxx/apache2/logs/login_log" xxxlogheader env=login_jsid
RequestHeader
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 3/22/18 10:11 AM, Rainer Jung wrote:
> Am 22.03.2018 um 15:07 schrieb Rainer Jung:
>> Am 22.03.2018 um 11:58 schrieb Martin Knoblauch:
>>> Hi,
>>>
>>> we have this annoying problem that although Tomcat workers are
>>> set to DIS state
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 3/22/18 6:58 AM, Martin Knoblauch wrote:
> we have this annoying problem that although Tomcat workers are set
> to DIS state in mod_jk, there are new connections being opened.
> This prevents us from "idle down" Tomcats in a timely
Am 22.03.2018 um 15:07 schrieb Rainer Jung:
Am 22.03.2018 um 11:58 schrieb Martin Knoblauch:
Hi,
we have this annoying problem that although Tomcat workers are set
to DIS
state in mod_jk, there are new connections being opened. This prevents us
from "idle down" Tomcats in a timely fashion.
Am 22.03.2018 um 11:58 schrieb Martin Knoblauch:
Hi,
we have this annoying problem that although Tomcat workers are set to DIS
state in mod_jk, there are new connections being opened. This prevents us
from "idle down" Tomcats in a timely fashion. This hurts when a restart is
needed. While our
Hi,
we have this annoying problem that although Tomcat workers are set to DIS
state in mod_jk, there are new connections being opened. This prevents us
from "idle down" Tomcats in a timely fashion. This hurts when a restart is
needed. While our empathy for human clients is pretty limited, we
