Re: Tomcat Crashed when the concurrent Users reached 150

2019-12-08 Thread Jayaram Ponnusamy
Thanks for your Valuable Comments: We are using Apache Tomcat/8.0.50 and Mod_JK mod_jk/1.2.28 The Above configuration made by some consultant. We are in the situation to correct all the things to make it for high availability. Also we are in the process of upgrading the apache to 2.4.25 with

Tomcat is throwing an error Invalid byte tag in constant pool:19

2019-12-08 Thread Nelligan, Steven M
I am trying to rebuild my applications and all of a sudden, I am getting the following error: Our backend application (from third party has been updated) It is using Java 11. My tomcat servers are running version 7.34 of tomcat and version 1.7.0_45. I have rebuilt and deploy a large number of

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

2019-12-08 Thread Jerry Malcolm
On 12/8/2019 6:23 AM, Mark Thomas wrote: On 08/12/2019 12:19, Mark Thomas wrote: Jerry, From your description, it sounds as if there is something about those requests that either isn't quite right or triggers an edge vase bug in Tomcat's request parsing. I'm happy to provide some pointers to

Design Patterns in Tomcat

2019-12-08 Thread M. Manna
Hi All, A numpty question as its best, but I was trying to summarise the design patterns used for tomcat. So far I could see the following, but shouldn't be limited to: 1) Mediator 2) Observer 3) Factory 4) Builder 4) Adapter Perhaps I missed any confluence link or something that confirms it?

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

2019-12-08 Thread Mark Thomas
On 08/12/2019 12:19, Mark Thomas wrote: > Jerry, > > From your description, it sounds as if there is something about those > requests that either isn't quite right or triggers an edge vase bug in > Tomcat's request parsing. > > I'm happy to provide some pointers to help you debug this. I'll use

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

2019-12-08 Thread Mark Thomas
Jerry, >From your description, it sounds as if there is something about those requests that either isn't quite right or triggers an edge case bug in Tomcat's request parsing. I'm happy to provide some pointers to help you debug this. I'll use 9.0.x links since I assume you prefer to debug this

Re: ServletRequest Obj Randomly not Processing x-www-form-urlencoded parms

2019-12-08 Thread Mark Thomas
Jerry, >From your description, it sounds as if there is something about those requests that either isn't quite right or triggers an edge vase bug in Tomcat's request parsing. I'm happy to provide some pointers to help you debug this. I'll use 9.0.x links since I assume you prefer to debug this

Expected behavior of calling javax.servlet.ServletRequest#getInputStream after javax.servlet.http.HttpServletRequest#getPart

2019-12-08 Thread Behrang Saeedzadeh
Hi, If I call javax.servlet.ServletRequest#getInputStream after having called javax.servlet.http.HttpServletRequest#getPart, even without performing any operations on the given part, I am getting an empty stream (0-bytes). Is this in compliance with the spec? Best regards, { "blog" :