Gary, This is a known bug that also affects merb/master. I'm not really familiar with those parts of the code, but here's a excerpt from a conversation with someone on irc who summarized it as follows:
"The background worker is started after you fork the spawner, but before you fork workers so, although the workers each have their own work_queue (which is getting filled up), none of them have a background worker thread to process the queue." A patch for that would be highly appreciated :) snusnu On Fri, Jan 1, 2010 at 02:26, Gary Yngve <[email protected]> wrote: > So on 1.0.15, I added some logging regarding run_later, initializing a > worker, and entering the work loop.. > > I get: > > > initializing! [82326, false, 0] > in worker! [82326, false, 0] > QUEUEING! [82327, true, 0] > > and nothing else.. > where 82326 is the PID of the spawner, 82327 is the PID of one of the > merb workers, the boolean is Merb::Worker.started?, and the number is > the size of the queue. > > i trigger a few more requests.. > QUEUEING! [82327, true, 1] > QUEUEING! [82327, true, 2] > QUEUEING! [82327, true, 3] > > the queue isn't being emptied.. > > The problem is the Worker should have been initialized in PID 82327, > right? > > -Gary > > -- > > 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. > > > -- 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.
