On Sun, Oct 01, 2006 at 04:39:07PM -0700, Zed A. Shaw wrote: > Ok, is there a way to fix this without having people backpatch their > ruby? Also, why were you the only one having this problem? I'd like > to know how the error is caused if you could explain it.
I'm not sure about this. I'll investigate further and see what I can come up with. > > The second problem stems from the fact that Mongrel uses the > > Thread#abort_on_exception. I'm not sure why this is even in there, as > > the documentation says: > > > > When set to true, causes all threads (including the main > > program) to abort if an exception is raised in thr. The process > > will effectively exit(0). > > > > The patch simply removes the abort_on_exception from mongrel.rb. After > > applying this patch I have been unable to make Mongrel crash. > > > > The abort was put in there to catch exceptions that are "leaking" > through and not being caught. I'm curious what exception was being > thrown that *none* of the damn begin/rescue blocks catches. We > seriously need a begin/rescue-every-damn-thing-no-matter-what > construct that actually works. > > Now, I believe the problem you'll have is when this exception leaks > through that thread will become dead and eventually you'll fill up and > Mongrel will die anyway. If you can, try to find out what exception > causes this so I can have the server kill off its threads properly by > handling this yet another annoying random exception. I'm not sure this is really a problem. It seems that threads are killed of nicely anyhow. But I'll dig into it and report back on this one too. -- Cheers, - Jacob Atzen _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
