Ok. That didn’t seem to work. I will investigate further and try to find a way to send that information.
It is not that busy a server, but the memory use increases very quickly. Doing a class_histogram shows MessageBytes growing by the thousands every 30 minutes. (We have a temporary monitor script in place that does a GC and then prints a class_histogram every half hour to help us pinpoint what is happening.) Thanks, Mark From: Mark A. Claassen <mclaas...@ocie.net> Sent: Thursday, July 8, 2021 5:07 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: RE: [Possible Spam] Re: HTTP/2 Memory Leak Importance: Low Thanks for the prompt reply. The system was not that busy. Having over 80,000 seems wrong. I am going to try to send a picture; I am not sure if this will work. This is from the Netbeans profiler. [cid:image001.png@01D7741B.B7CC7D90] -----Original Message----- From: Mark Thomas <ma...@apache.org<mailto:ma...@apache.org>> Sent: Thursday, July 8, 2021 2:46 PM To: users@tomcat.apache.org<mailto:users@tomcat.apache.org> Subject: [Possible Spam] Re: HTTP/2 Memory Leak Importance: Low Memory leak, high memory usage or high GC churn? The StreamProcessor shouldn't be a GC root. Either something should be retaining a reference to it or it should be eligible for GC. There isn't much in the way of HTTP/2 specific leaks that have been fixed. For HTTP/2, I'd expect you to see much more impact from the changes around 9.0.37 / 9.0.39 that reduced the footprint of closed HTTP/2 streams. Mark On 08/07/2021 19:32, Mark A. Claassen wrote: > Sorry, realized I had a mistyped subject. > > -----Original Message----- > From: Mark A. Claassen <mclaas...@ocie.net<mailto:mclaas...@ocie.net>> > Sent: Thursday, July 8, 2021 2:30 PM > To: Tomcat Users List > <users@tomcat.apache.org<mailto:users@tomcat.apache.org>> > Subject: Http/s Memory Leak > Importance: Low > > We are using 9.0.12 on a server and noticed a pretty big memory leak. The > change log mentions a some fixed leaks in the releases since 9.0.12. > I was wondering if this leak was fixed already. > > The leak is that there are over 80,000 instances of > org.apache.tomcat.util.buf.MessageBytes. Below is the reference path. > Is this one of the things fixed by setting useAsyncIO="false"? Is there a > downside to using this? > (We are using Http11AprProtocol and OpenSSL) > > Thanks, > Mark > > Reference path of the leak: > MessageBytes > MimeHeaderField > MimeHeaderField[] > MimeHeaders > Response > Stream > ConcurrentHashMap$Node > ConcurrentHashMap$Node > ConcurrentHashMap$Node[] > Http2UpgradeHandler > StreamProcessor (Root) > > Mark Claassen > Senior Software Engineer > > Donnell Systems, Inc. > 130 South Main Street > Leighton Plaza Suite 375 > South Bend, IN 46601 > E-mail: mailto:mclaas...@ocie.net > Voice: (574)232-3784 > Fax: (574)232-4014 > > Disclaimer: > The opinions provided herein do not necessarily state or reflect those of > Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal > liability or responsibility for the posting. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: > users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: > users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org> For additional commands, e-mail: users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org>
