Are you running a debugger?
On 3/15/19, Mark Thomas wrote:
> On 15/03/2019 17:51, Shankar P S wrote:
>> @Mark Thanks for the tip. I compared the 2 heap dumps. For the same
>> server.xml config, 8.5.38 version of Tomcat creates 3 StandardContext
>> instances. I see that these 3 objects have their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 3/15/19 19:49, Mark Thomas wrote:
> On 15/03/2019 17:51, Shankar P S wrote:
>> @Mark Thanks for the tip. I compared the 2 heap dumps. For the
>> same server.xml config, 8.5.38 version of Tomcat creates 3
>> StandardContext instances. I see
On 15/03/2019 17:51, Shankar P S wrote:
> @Mark Thanks for the tip. I compared the 2 heap dumps. For the same
> server.xml config, 8.5.38 version of Tomcat creates 3 StandardContext
> instances. I see that these 3 objects have their own hierarchy.
>
> *Tomcat 8.5.38 - 3 instances of
@Mark Thanks for the tip. I compared the 2 heap dumps. For the same
server.xml config, 8.5.38 version of Tomcat creates 3 StandardContext
instances. I see that these 3 objects have their own hierarchy.
*Tomcat 8.5.38 - 3 instances of StandardContext*
First instance originalDocBase
On 14/03/2019 21:15, Shankar P S wrote:
> Version - Tomcat 8.5.38
> OS - Centos 7.6
> JVM - openjdk 1.8, 4 CPU
>
> We recently upgraded an existing server running a Spring 3.0 web app from
> Tomcat 8.5.35 to 8.5.38.
>
> After the upgrade, I noticed OutOfMemory exceptions several times.
>
Version - Tomcat 8.5.38
OS - Centos 7.6
JVM - openjdk 1.8, 4 CPU
We recently upgraded an existing server running a Spring 3.0 web app from
Tomcat 8.5.35 to 8.5.38.
After the upgrade, I noticed OutOfMemory exceptions several times.
Increasing the heap size (-Xmx) several times upto nearly twice
