Problem with Memcache / forking

[jerrett]

http://www.modrails.com/documentatio...haring_harmful


I'm running into a similar problem with Litespeed... Memcache is returning incorrect objects, sometimes.

Any ideas of a solution? How would one go about reseting the connection to memcache each time it's forked, if this is the problem?

[jerrett]

This also just started happening with the new Litespeed and Rails 2.3 (Rack)..

[mistwang]

Yes, need to reset the connection to memcache. Just close all connections after the initialization.

[jerrett]

Would it be a good place to do this in environment.rb, or is that not going to get executed when it's forked?

[mistwang]

It should be fine. environment.rb only get loaded once I think.

[jerrett]

Doesn't seem to help, if it's only loaded once i'm assuming that means it won't reset when the process gets forked.. where would we hook into that?