Ok, so, I’ve read ticket #428 forwards, backwards, and sideways… and up until a few days ago, had never had a problem.
However, I now have one.
One of my applications, due to a plugin, was accessing the DB during the loading of routes.rb… which is apparently before the reconnect! message is sent to the connection. I was coming up with the exact same problems addressed by ticket #428 on the rails trac. I put an easy fix into the plugin by directly calling reconnect! unless active?, but I was wondering if this process shouldn’t take place before loading routes.rb by default, so as to avoid having this problem in the future.