This must be my day... I am stress testing a new application that uses apache::session with the DB_File backend store. When hitting it with apache bench after a few hundred connections something with the db file gets wacked, and apache starts to segfault until I delete the .db file, at which point everything is ok again.
The code in Apache::Session::Store::DB_File does not look safe to me. It doesn't untie the file between writes, which is a problem with DB_File because of the built-in caching it uses. If you just want safe access to DB_File from multiple processes, you should try MLDBM::Sync instead. If you want to use Apache::Session, switch to the MySQL or file storage instead.
- Perrin
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
