https://issues.apache.org/bugzilla/show_bug.cgi?id=44975
--- Comment #27 from Michael Chen <[email protected]> 2009-01-21 14:55:42 PST --- (In reply to comment #26) > My mistake, after double-checking this the OpenSSL code in question appears to > be in 0.9.8e and later. > Another known memory leak in mod_ssl is the dbm session cache. I've done some more investigation by taking the source code from 2.2.10 and build it and use our current httpd.conf from 2.0.x. To my surprise, I can still reproduce the problem with the source code in 2.2.10. If download 2.2.10 installer and use that, the problem does not exist. I then do a diff and migrate the change one by one using httpd.conf from 2.2.10 to the one from 2.0.x and identify the source of the problem. This is the settings in httpd-ssl.conf from Apache 2.2.10. # to use and second the expiring timeout (in seconds). #SSLSessionCache "dbm:c:/cache/2210-2/out_nti86/iw-webd/logs/ssl_scache" SSLSessionCache "shmcb:c:/cache/2210-2/out_nti86/iw-webd/logs/ssl_scache(512000)" SSLSessionCacheTimeout 300 This is the settings in ssl.conf from apache 2.0.x. #SSLSessionCache none #SSLSessionCache shmht:logs/ssl_scache(512000) #SSLSessionCache shmcb:logs/ssl_scache(512000) SSLSessionCache dbm:logs/ssl_scache It means that in Apache 2.2.x, shmcb/path/to/cache is used while in Apache 2.0.x, dbm/path/to/cache is used which causes the problem. In Apache 2.2.10, if I switch to use dbm/path/to/cache, I can reproduce the problem. In Apache 2.0.x, if I switch to use /shm/path/to/path, the problem goes away. After I found this, I did a search to see if there is any mod_ssl/SSLSessionCache issue which causes the memory memory leak and I did find it at https://issues.apache.org/bugzilla/show_bug.cgi?id=25667 I am not sure why bug 25667 is left open and the solution is just to fix the configuration file and update the doc so that user using apache 2.0.x will be aware of that? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
