On Mon, Jun 11, 2012 at 11:38:36PM -0700, Reed Law wrote: > > > What version of ruote are you using? > > I'm on the latest Github HEAD (a9d289744cc84c816c66f59ad061f08ba1b8f748) > but it's been happening for several months.
Hello, ouch, I wished you had reported the issue earlier. > > What's the context in which you're using ruote? (Rails, Sinatra, > > Passenger, > > ...) > > Rails 3.2.5 with ruote-kit (also latest HEAD) You forgot to mention Unicorn (you did in https://github.com/jmettraux/ruote-redis/issues/3 ;-) ) > > What storage are you using for ruote? > > Was using ruote-redis, now ruote-mon Ouch, according to the issue mentioned above, you switched to ruote-mon today. Is it happening with ruote-mon too? If yes if you could respond to the answer at the end of this email (What stucks... and co) > > What's behind the storage? (Database, version)? > > MongoDB 2.0.6 What Redis was it ? > > What does your process definition look like? > > See http://www.hastebin.com/gosiqosoti.pl OK, I'll reverse engineer the definition. Do you have the output for the two expressions in that process? > > What does your "kill" scenario read like? > > I am trying to kill or cancel the stuck process through ruote-kit's web > interface (http://0.0.0.0:3000/_ruote) How does a process end up stuck? > > What more should I know? > > This issue is not limited to my present setup but I've experienced it on > each platform I've used. In the fluo representation the stuck processes > have a green marker that isn't on any participant but on the edge of an > expression. In my app I delete processes > with RuoteKit.engine.kill_process(wfid). That method sometimes leaves them > in a stuck state. In ruote-kit sometimes killing a process produces errors > that, once cleared, allow the process to be deleted. Other times clearing > the errors still leaves me with a stuck process. I wish I could see one of those errors. I wish I could see one of those stuck processes. What stucks the process in the first place? Is the stucking always happening around the same expression? What do those "sometimes errors" look like (message, type, backtrace)... For the redis issue you reported I'll try to come up with a reconnect thing, stay tuned. Thanks in advance, -- 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
