On Dec 11, 4:19 pm, "Dan Kubb (dkubb)" <[email protected]> wrote:
> Yeah, offhand I can't think of any reason why there's an open DB > connection prior to spawning workers. It's not like DM does any DB > introspection or anything when setting up it's Models. In my case it was caused by some application specific startup stuff attached to BootLoader.after_app_loads. I've worked around it by forking off another process to do the datamapper bits, since only their side effect in the persistent store was needed. I can easily imagine cases where that wouldn't work though, and the sockets would need to be closed before the spawner reaches its final configured state, or they would need to be closed more or less immediately in the forked worker. -john --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
