Sorry... forgot the version. You are correct. It's 8.5.x running on
AWS Linux EC2. I didn't intentionally configure anything special for
the pool. So I assume it's dbcp 2.0. Here is my resource config:
I didn't notice the problem for a couple of days. Then it blew up on a
Am 24. Januar 2020 06:22:49 MEZ schrieb Jerry Malcolm :
>
>On 1/23/2020 11:04 PM, Jerry Malcolm wrote:
>> Sorry... forgot the version. You are correct. It's 8.5.x running on
>
>> AWS Linux EC2. I didn't intentionally configure anything special for
>
>> the pool. So I assume it's dbcp 2.0.
On 1/23/2020 11:04 PM, Jerry Malcolm wrote:
Sorry... forgot the version. You are correct. It's 8.5.x running on
AWS Linux EC2. I didn't intentionally configure anything special for
the pool. So I assume it's dbcp 2.0. Here is my resource config:
On 22.01.2020 10:26, Lmhelp1 wrote:
Hello Chris and all,
Sorry for my late answer.
Thank you for the link you suggested me to read.
Adding the element:
UTF-8
to "web.xml" solved my problem.
Glad to hear that.
From an absolute point of view, this is of course again a "patch". But as Chris
Hi, we started noticing that HttpServletRequest.getRemoteAddr() was
sometimes returning NULL (which is invalid according to the servlet
spec), about 20-50 times per day (we have high-load servers which
routinely handle over 100 requests per second). This only happens on
secure HTTP/2 requests.
Hi Michael,
Thank you I will update and observe, interesting that the crash only happens on
this machine, we have 3 other machines with the same setup which I don't see
the crashes.
Warm regards,
Norbert Elbanbuena
-Original Message-
From: Michael Osipov
Sent: Thursday, January
