Hi John,
Thanks very much for the reply; great to know that I was on the right track
and I think I've got everything working. I started with your questions and
found the following:
> ::RuoteDashboard.processes
=> []
> ::RuoteDashboard.errors
=> []
> ::REDIS.llen('msgs')
=> 0
Even when I launched a definition directly, `RuoteDashboard.processes`
remained an empty array even though a workflow id was returned:
> RuoteDashboard.launch(t.process_definition, {"task" => {"id" =>
t.id.to_s, "input" => t.input}})
=> "20120203-disokesa"
> RuoteDashboard.processes
=> []
> RuoteDashboard.errors
=> []
So I double checked my Redis configuration, which was:
Resque.redis = Redis.new(:host => uri.host, :port => uri.port, :password =>
uri.password, :thread_safe=>true)
Resque.after_fork do |job|
Resque.redis = Redis.new(:host => uri.host, :port => uri.port, :password
=> uri.password, :thread_safe=>true)
end
::REDIS = Resque.redis
Resque namespaces its connection so ::REDIS was namespaced to "resque",
which seems to be what was causing ruote not finding processes. Changing my
config to the following seems to have fixed things up:
::REDIS = Redis.new(:host => uri.host, :port => uri.port, :password =>
uri.password, :thread_safe=>true)
Resque.after_fork do |job|
Resque.redis = Redis.new(:host => uri.host, :port => uri.port, :password
=> uri.password, :thread_safe=>true)
end
Resque.redis = ::REDIS
I'll keep an eye on things and let you know if any other issues come up
with running this type of configuration on Heroku.
Thanks!
Chris
--
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
