I'm sure not if it's before or after, but what I can say is that this is from Passenger's docs:
The problem commonly involves socket connections that are unintentionally being shared. You can fix it by closing and reestablishing the connection when Phusion Passenger is creating a new worker process. Phusion Passenger provides the API call `PhusionPassenger.on_event(:starting_worker_process)` to do so. It would be nice if the name was clearer but this might actually take place before the fork. Here's further docs on the matter: Note that Phusion Passenger automatically reestablishes the connection to the database upon creating a new worker process, which is why you normally do not encounter any database issues when using smart spawning mode. Take that for what it's worth. My testing is still pretty early in the day, but I haven't run into this issue since implementing these changes. I'll update this further if anything changes on that front. Thanks again for your help. -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
