Am 11.01.19 um 18:23 schrieb Mark Thomas: > Found it. > > The leak impacted NIO and NIO2 when used with OpenSSL. > > The bug is in Tomcat Native. I have a fix that I am currently testing. > That fix should be in the next Tomcat Native release. > > For those interested in the technical details, Tomcat Native allocates > some Native memory to track various attributes of each connection. > > In APR/Native this memory is allocated from a new APR memory pool that > is associated with the connection. When the connection closes, the pool > is destroyed and the memory freed. All is good. > > In NIO[2]+OpenSSL the per connection memory was allocated from the APR > memory pool associated with the Connector so the memory was not released > until the Connector was stopped. The fix is to create a pool per > connection and use that for the per connection allocations. With a fix > to do that in place, memory use is now broadly static under extended TLS > load. > > Mark >
Thanks Mark! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
