Hi everyone, I've got a problem that has me stumped.
I've got an application running rails 2.3.8, ruby 1.8.7. I'm using the Activerecord Session store with MySQL. On my development site, the session table's updated_at column has its timestamp updated on every request. On my production site the behavior is very erratic. Some sessions update some of the time, others never change from the created_at time, and there's no apparent link behind who gets updated and who doesn't. I've been tearing my hair out with this, and I'm not finding anything with Google. Is there something inherently different about how sessions are handled in production vs. development? Can anyone suggest a place to start looking? I'm lost because it's working perfectly on my development machine. I'm wondering if it's a traffic based thing - since my development machine has generally less than 5 or 6 users on it at a time, while the production site can have hundreds of users active at any given moment. Other than that, I'm at a loss. Any ideas? Thanks so much, Andrew -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
