I, too had a similar problem - which persisted even after I inserted this: ActiveRecord::Base.verification_timeout = 14400
Into my config/production.rb On close inspection of my apache logs I discovered that a robot was hitting my application with a (near) simultaneous pair of get requests with identical session_id's. The session_id was new - and so both rails processes attempted to insert a new record into the session table, causing the database to report a duplicate key violation on the second insert. Apparently the second rails process determined that the session_id was new before the first rails process had finished its insert. Hope this is helpful. Robert _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users