Hello,
for some reason my singleton resources display strange behaviour after upgrading to Rails 3:
- when I first start my application, or restart it, they work normally.
- subsequent reloads (in devel mode) display the above error message.
The same thing happens when using Apache with Passenger and instead of (re)starting, doing "touch tmp/restart.txt".
All normal resources, and all resources inheriting from ApplicationController and then using the "resource_controller" keyword, still work as expected.
I use Rails 3.0.5, Apache 2.2 with Passenger 3.0.3.
Is this a known bug?
If not, how can I track it down?
Thank you!
Regards
Jens