Hello Mark,
I could test the change today, unfortunately only with moderate
success. The change to %a or %h, unfortunately did not work, but the
readout with the header value per %{X-Forwarded-For}i worked. The log
doesn't look nice, but we get the value. Nevertheless I am still
looking for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sathis,
You have run across this known bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64097
Please read that bug report for more details, particularly comment #8.
Hope that helps,
- -chris
On 4/3/20 11:05, sathis kumar wrote:
> --
On 03/04/2020 16:33, sathis kumar wrote:
> Thanks much for your response. I am using the el-api.jar coming along with
> Tomcat9.0.31/lib - Still a sample problem..
> JDK version we are using is - > 1.8
Please provide the simplest possible set of steps to recreate this error
from a clean Apache
-- Forwarded message -
From: sathis kumar
Date: Fri, Apr 3, 2020 at 9:38 AM
Subject: Tomcat 9.0.31 - BUG
To:
My Application is working fine in prev version of all tomcat, Planning to
upgrade to 9.0.31
. I am running into the following issue.. Pls help
Thanks much for your response. I am using the el-api.jar coming along with
Tomcat9.0.31/lib - Still a sample problem..
JDK version we are using is - > 1.8
On Fri, Apr 3, 2020 at 11:16 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
*Tomcat Users List >, *
*"Thans for your reply.. When i tried with simple JSP", "worked. Fine..
When i tried deploying my other application", "ran into that issue :("*
javax.servlet.ServletException: javax.el.ELException: Unable to find
ExpressionFactory of type: # Licensed to the Apache
On 03/04/2020 19:04, sathis kumar wrote:
> *Tomcat Users List >, *
> *"Thans for your reply.. When i tried with simple JSP", "worked. Fine..
> When i tried deploying my other application", "ran into that issue :("*
That points to an application problem, not a Tomcat problem.
You need to remove
For the past few months we’ve been trying to trace what looks like gradual
memory creep. After some long-running experiments it seems due to memory
leaking when
jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*,
JNI_ArgumentPusher*, Thread*) is invoked. Somewhere.
My
