There isn’t a memory leak I'm aware of. At least nothing is reported from what
I can find. Have you tried setting maxActiveSessions? Its default is -1 which
means infinite. Also there could be a bug in the code that is just creating new
sessions for things instead of using the current session.
Shawn Beard • Sr. Systems Engineer
Middleware Engineering
[cid:image498464.png@B1B8F0D2.A7934045]
3840 109th Street , Urbandale , IA 50322
Phone: +1-515-564-2528<tel:+1-515-564-2528>
Email: sbe...@wrberkley.com<mailto:sbe...@wrberkley.com>
Website: https://berkleytechnologyservices.com/
[cid:image170342.jpg@8D7E010B.AF86CC81]
Technology Leadership Unleashing Business Potential
-----Original Message-----
From: Tim K <tim.k.5...@gmail.com>
Sent: Tuesday, October 19, 2021 6:35 AM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Potential Memory Leak with StandardManager [EXTERNAL]
** CAUTION: External message
On Mon, Oct 18, 2021 at 2:51 PM Beard, Shawn <sbe...@wrberkley.com.invalid>
wrote:
> Update to Tomcat 9.0.54. This could be a known security bug that is
> fixed in this version.
>
> https://urldefense.com/v3/__https://tomcat.apache.org/security-9.html*
> Fixed_in_Apache_Tomcat_9.0.54__;Iw!!Li8W9_Um1Taa!uj_ntV4p2gMeMsLvxyGG7
> 2U9DIPWfNyVeqRi0mD7H1ane3v6ToErlw4gMB9DVcrh$
>
I tried updating to that version but it does not appear to be related; that
looks to be related to web socket connections.
CONFIDENTIALITY NOTICE: This e-mail and the transmitted documents contain
private, privileged and confidential information belonging to the sender. The
information therein is solely for the use of the addressee. If your receipt of
this transmission has occurred as the result of an error, please immediately
notify us so we can arrange for the return of the documents. In such
circumstances, you are advised that you may not disclose, copy, distribute or
take any other action in reliance on the information transmitted.
