Weird problem with Rails app and Mongrel?

I had a similar problem where my Rails app would run fine under WEBrick but not under Mongrel but found somewhere on the internets ( here's a link that shows a similar version of the problem) that older versions of Mongrel mishandle the first request to the page but handle subsequent requests ok The workaround we put in was that whenever we started the app, we'd have curl perform a GET on the app to 'prime' Mongrel.

I had a similar problem where my Rails app would run fine under WEBrick but not under Mongrel but found somewhere on the internets (here's a link that shows a similar version of the problem) that older versions of Mongrel mishandle the first request to the page but handle subsequent requests ok. The workaround we put in was that whenever we started the app, we'd have curl perform a GET on the app to 'prime' Mongrel.

It is on every request – trobrock Jun 30 '10 at 23:49.

This is usually a fail reading a yaml file for config. It has set up a config object to get values from and the entry in the yaml file for your environment isn't there so the object is nil. Are you running any gems that have a yaml file that maybe isn't set up for development?

I don't know why going back to 2.3.5 would help - it might be that it loads things in a different order and the config information is available.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.