On Wed, Apr 30, 2008 at 6:13 AM, Maarten <[EMAIL PROTECTED]> wrote: > > I have run into a problem with long sleeps in my processes. I have > several sleeps in my processes from several minutes up to 12 hours. In > certain process instances the 12h sleeps result in the exception > below. This is when the scheduler gets a trigger and needs to wake up > the process. Because of this error the process instance hangs and > won't continue. > > Strangely sometimes it works. I use OpenWFE::Extras::DbPersistedEngine > in a two-instance load balanced mongrel setup. I don't have any other > issues with the database. > > trigger() caught exception > Mysql::Error: MySQL server has gone away: DELETE FROM expressions > WHERE (fei = '(fei 0.9.17 engine field:__definition the_leader_in_me > 0.9 20080424-juhizagepo sleep 0.0.14)') > > (...) > > Anyone seen these kind of errors before? Anyone ideas why just this > specific operation might result in Mysql errors?
Hi Maarten, I did a quick search : http://www.google.com/search?q=%22%20Mysql%3A%3AError%3A%20MySQL%20server%20has%20gone%20away%22 It seems that the most relevant answer is at : http://rubyforge.org/pipermail/backgroundrb-devel/2006-July/000126.html But maybe the other links have more information. It seems that setting ActiveRecord::Base.allow_concurrency = true Would do the trick. Tomaso, IIRC you are using the DbPersistedEngine (or the Cached) one in production (and you're the Author ;) ), did you encounter this issue somehow ? Best regards, -- John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" 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/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
