Hi John, Thanks for looking into this. We have time to test mysql. At the moment, though, we are going to try setting up Redis. We have it up locally, but we are reverse-engineering how our DevOps team deploys redis - (No DevOps here in Japan, but in the US).
Chad On Thursday, July 26, 2012 6:53:31 PM UTC+9, John Mettraux wrote: > > > On Thu, Jul 26, 2012 at 02:14:29AM -0700, Chad wrote: > > > > I regret to say that the Passenger solution is not holding. We continue > to > > experience the disconnects. It just takes alot longer. Once ruote (or > > ruote sequel) encounters one disconnect, this appears to be the > behavior: > > Ruote continues to accept incoming requests, but > process_def/participants > > are in limbo. They are added to the database, and issued an id. > However, > > they are unknown if we attempt to find them with engine.process(the-id). > > Sounds right, once the connection is borked, there is nothing much > ruote-sequel can do... > > But wait, what is strange is that Engine#process(wfid) should raise that > same > disconnect error when being called... I will investigate that. > > > When then restart our webservice built around Ruote, and, of course, a > new > > engine is created, connecting to the database. Now, the engine starts > > doing its work, and engine.process(the-id) finds the process. > > > > Does this sound familiar? Any advice? > > No, it doesn't sound familiar (unlike the post fork disconnects). > > Would you still have time to test with "mysql" (instead of "mysql2")? > > Their sequel drivers seem to have different reconnection code, so I'd love > to > know how mysql holds. Maybe mysql2 and sequel are not in sync (I'm > probably > wrong since Mysql2 0.3.11 is from December 2011, while Sequel 3.37.0 is > from > July 2012, but I need to know anyway). > > Meanwhile I'll investigate those silent Engine#process(wfid) failures you > mentioned. > > Cheers, > > -- > John Mettraux - http://lambda.io/jmettraux > -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
