Hi ruote users.
We recently upgraded to the (unreleased) ruote 2.2.1 (because we
needed the upgrades in ruote-redis and redis-rb) and ever since the
worker can't find some of the participants for the workflow
intermittently... this happens on average for about 1 out of 50 or so
expressions...
The full stack trace from ruote kit is:
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/exp/fe_participant.rb:141:in `apply'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/exp/flow_expression.rb:319:in
`do_apply'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/worker.rb:381:in `launch'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/worker.rb:284:in `process'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/worker.rb:198:in `step'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/worker.rb:93:in `run'
/srv/www/jasperdocs-production/shared/bundle/ruby/1.9.1/bundler/
gems/ruote-b66b34f1315c/lib/ruote/worker.rb:104:in `block in
run_in_thread'
The weird thing is, that replaying the expression fixes it and the
workitem happily continues its way through the workflow.
Any ideas?
For completeness, here's our stack:
* ruote - 2.2.1 (from github) - ref
b66b34f1315c4bc99acec8d5db07e62160a4b896
* ruote-redis - 2.2.1 (from github) - ref
cdb5712aa05f8717962898f9a9a3cd283d5de971
* ruote-kit - 2.2.1 (from github) - ref
191817aa92715b40b377ce0c28293382a6c47efd
* redis-rb - 2.2.2
Thanks for your help.
Cheers,
Tom
--
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
