On 18 Nov 2008, at 00:21, Nik B wrote:
> > I have a vexing problem where a request is completed and customer > information is stored in session (to be deleted on successful > checkout). After the request completes, any subsequent action throws a > Internal Server Error 500. > You're storing soap objects in your session ? I'm guessing wildly but I'd guess that what's in the session references a class that was unloaded between the two requests, so the unmarshaling code fails horribly (if turning config.cache_classes on makes the problem go away then that would be a strong indication that something of that nature is the problem). One way around this would be to only store primitive types like arrays and hashes in the session. Fred > This is the stack trace: > > http://pastie.org/317365 > > Could I be storing too much information in session? It's merely an > address... > > Debugging sessions problems is poo. > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
