Issue solved. It was apache caching cookie information - who would
have thought. I found my answer from this article
http://issues.apache.org/bugzilla/show_bug.cgi?id=42935
More info about caching cookie can be found here
http://httpd.apache.org/docs/2.2/en/mod/mod_cache.html#cacheignoreheaders
On Oct 15, 2:53 pm, mahnovetsky
<rmahnovet...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Hi guys
>
> We have a really bad issue with our rails app. Sometimes a logged in
> user who has been browsing around for a bit will be logged in as
> someone else. This only happens sometimes which is making this a
> really difficult issue to track down.
>
> The current set up is with apache which also acts as a load balancer
> and 4 mongrels. We use memcached to store the session.
>
> It seems like the session id or cookie is being cached and then handed
> to mongrel. Mongrel then hands back info for some other user. Or maybe
> it is some memcached issue with mongrel not handling concurrently
> correctly. Really baffled as to why this is happening.
>
> Any help will be appreciated. TIA
--~--~---------~--~----~------------~-------~--~----~
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-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---