[Ruby] Any help on how to debug a Rails RuntimeError?

ben wiseley wiseleyb at gmail.com
Sun Apr 22 10:21:11 PDT 2007


On 4/22/07, James Hillyerd <james at hillyerd.com> wrote:
>
> On 4/22/07, Joe Shapiro <joeshapiro at gmail.com> wrote:
> > Hi Folks
> > I've got an app that seems to be clobbering its session data. The
> session_id
> > is correct but the data within it seems to be all cleared out. Under
> mongrel
> > I don't see an error raised but under webrick I get the lengthy
> backtrace
> > which follows this message. Can anyone offer any suggestions of how to
> wrap
> > my head around this one? Thanks for any help you folks can offer. If I
> can't
> > get it solved before then I'll probably be at hack night Tuesday lookin'
> for
> > some help...
> >
>
> A shot in the dark, but...
>
> One of the problems we ran into when we switched to memcache sessions
> was that Ruby didn't know about certain model objects at the time it
> was trying to unmarshall them.  This was especially apparent when you
> have more than one app server accessing the cache.
>
> There are a number of documents out there describing how to pre-load
> your models so that Ruby is aware of them at "boot".  Although I
> thought the latest versions of Rails did this on their own.
>
> -james
>
> --
> James A. Hillyerd <james at hillyerd.com>
> Chief Technical Officer - ActiveRain Corp
> _______________________________________________
> Ruby at zenspider.com - Seattle.rb non-commercial list
> http://www.zenspider.com/seattle.rb
> http://www.zenspider.com/mailman/listinfo/ruby
>

Actually - (James and I work together) we're doing this explicitly in
application.rb with a 'require [model name]' at the top of the file.

-ben


More information about the Ruby mailing list