No thread name in AccessLogValve printed

2020-10-20 Thread Michael Osipov
Folks, I have seen recently entried like this on our access logs: 2020-10-19T20:00:05.591 [null] xyz - "-" 400 - 0 2020-10-19T20:00:05.591 [null] abc- "-" 400 - 0 2020-10-19T20:00:05.592 [null] abc - "-" 400 - 0 2020-10-19T20:00:05.593 [null] abc - "-" 400 - 0 2020-10-19T20:00:05.616 [null] abc

Re: No thread name in AccessLogValve printed

2020-10-20 Thread Mark Thomas
On 20/10/2020 10:10, Michael Osipov wrote: > Folks, > > I have seen recently entried like this on our access logs: >> 2020-10-19T20:00:05.591 [null] xyz - "-" 400 - 0 >> 2020-10-19T20:00:05.591 [null] abc- "-" 400 - 0 >> 2020-10-19T20:00:05.592 [null] abc - "-" 400 - 0 >> 2020-10-19T20:00:05.593 [

Re: No thread name in AccessLogValve printed

2020-10-20 Thread Michael Osipov
Am 2020-10-20 um 11:44 schrieb Mark Thomas: On 20/10/2020 10:10, Michael Osipov wrote: Folks, I have seen recently entried like this on our access logs: 2020-10-19T20:00:05.591 [null] xyz - "-" 400 - 0 2020-10-19T20:00:05.591 [null] abc- "-" 400 - 0 2020-10-19T20:00:05.592 [null] abc - "-" 400

Re: Virtual event focussed on Tomcat Security

2020-10-20 Thread Christopher Schultz
Mark, On 10/15/20 14:01, Mark Thomas wrote: > On 29/09/2020 12:25, Mark Thomas wrote: >> Hi all, >> >> We (the Tomcat community) have some funding from Google to help us >> improve Tomcat security. Our original plan was to use the funding to >> support an in-person security focussed hackathon. As

Re: [EXTERNAL] Re: Embedded vs Standalone Tomcat

2020-10-20 Thread Amit Pande
Thank you so much Igal for the inputs. Thanks, Amit Thanks, Amit From: Igal Sapir Sent: Sunday, October 18, 2020 11:36:22 AM To: Tomcat Users List Subject: [EXTERNAL] Re: Embedded vs Standalone Tomcat Amit, On Fri, Oct 16, 2020 at 8:32 AM Amit Pande wrote: >

Recent Tomcat crash produced error messages I've never seen before

2020-10-20 Thread James H. H. Lampert
We had a Tomcat crash on a customer box, a few hours ago (a simple restart got them back up and running), and it produced a whole bunch of errors in the general vein of *** Invalid JIT return address 0006E2E2E400 in 0001A83C5210 before finally failing with a null pointer exception, and

jstl jar location

2020-10-20 Thread George Stanchev
I am hoping someone can shed some lights on a question. I did try to search online and SO but haven't had luck in figure it out so hopefully it is a quick answer from the people that know that stuff. We have an uber-lib folder where we keep shared libraries in our TC85-hosted app. If we put jst

Re: Recent Tomcat crash produced error messages I've never seen before

2020-10-20 Thread Christopher Schultz
James, On 10/20/20 13:35, James H. H. Lampert wrote: > We had a Tomcat crash on a customer box, a few hours ago (a simple > restart got them back up and running), and it produced a whole bunch of > errors in the general vein of >> >> *** Invalid JIT return address 0006E2E2E400 in 0001A83C5

Re: Recent Tomcat crash produced error messages I've never seen before

2020-10-20 Thread James H. H. Lampert
On 10/20/20 1:26 PM, Christopher Schultz wrote: Theoretically, it should not be possible to cause a JVM to crash with pure Java code. Thanks. Of course, we all know that while theory and practice are the same in theory, they aren't always in practice. ;-P -- JHHL --

Re: Recent Tomcat crash produced error messages I've never seen before

2020-10-20 Thread Christopher Schultz
James, On 10/20/20 16:39, James H. H. Lampert wrote: > On 10/20/20 1:26 PM, Christopher Schultz wrote: >> Theoretically, it should not be possible to cause a JVM to crash with >> pure Java code. > > Thanks. > > Of course, we all know that while theory and practice are the same in > theory, they

RE: FW: HTTP2: memory filled up fast on increasing the connections to 1000/2000 (Embedded tomcat 9.0.38)

2020-10-20 Thread Arshiya Shariff
Hi, Christopher, Please find the answer in-line: How... exactly? private String getRequestBody(HttpServletRequest request) throws IOException { StringBuilder sb = new StringBuilder(); BufferedReader reader = request.getReader(); try