similar to: Problem with resque; parent process doesn't die

Hi, I have implemented resque scheduler in my application by looking at example here https://github.com/bvandenbos/resque-scheduler. I have configured resque_schedule.yml file, and in that I can pass arguments to the resque job. My requirement is to pass more than one arguments to the queueing resque job. If we consider the example given, clear_leaderboards_contributors: cron: "30 6 * *

I run Resque with x ''general'' queues. With ''general'' I mean a queue that may run every type of Worker. Or in the Rake command: COUNT=x QUEUE=* rake resque:work When a worker runs a job of a specific class, it may not run another job of the same class simultaniously. This job has to wait until the previous job has finished before it may start. BTW The reason

Hi, I''ve just got a quick question. How come ActiveRecord::ConnectionAdapters::ConnectionHandler#verify_active_connections! is marked with :nodoc: ? I understand that this is used internally (depending upon an application''s configuration?) on every request (?) to clear out old, stale database connections. All this to prevent the old, classic "MySQL server has gone

Hi, I am using resque, resque-scheduler gems in my rails app. To monitor the working of resque workers, I am using God tool. I want to add such a god configuration, which will monitor the time of job running in the resque worker. If process execution exceeds the time limit, then it should restart the worker. I read post at http://god.rubyforge.org/. However, couldn''t peek the right

I have two classes Person and Job defined as follows: class Person < ActiveRecord::Base :has_and_belongs_to_many jobs def add_job(job_name) job = Job.find_by_name(job_name) # See if this job exists if job.nil? # If this job doesn''t exist job = Job.new # Create a new job job.name = job_name #

When I run rake db:migrate or rake -T I get these lines at the end: Finished in 0.000276 seconds. 0 tests, 0 assertions, 0 failures, 0 errors My Gemfile is: source ''http://rubygems.org'' gem ''rack'' gem ''rails'', ''3.0.9'' gem "acl9", ''0.12.0'' gem "fastercsv"#, :version =>

While i run rake db:migrate i got below error ,let me know any one . Please it is urgent to me. D:\raj\tweasier>rake db:migrate --trace (in D:/raj/tweasier) DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart_2/tasks, vend or/plugins/resque/tasks, and vendor/plugins/resque/tasks are deprecated. Use lib /tasks instead. (called from

Hi, guys! Background: I''ve resque workers in my application. These workers do several jobs that associated with DB. In development environment, I''ve no need to provide some additional configuration for db, they are use development database. But then I switching to production env, I set ActiveRecord::Base.establish_connection with my production DB parameters. Problem: When

I''m loving playing around with the DSL. There are some problems (ie 5237), but now that it''s Ruby, I can fix them! woo! However, I''m stumped on this one, which may or may not be related to the DSL. When trying to have a resource have a simple dependency on two things at once, it simply fails, and I''m stumped as to why. The error message is: Parameter

For several months I've been thinking about moving to Linux operating system. This would resque our old machine which is getting left behind when it comes to hardware (and it would also put fun back into computing). The problem is that if I convert the only machine our family has to Linux, it would mean that an important program, Photoshop, which we use everyday has to be abandoned. This

Hi We are looking for a strong Ruby on Rails developer in Golden, CO. Post your resumes to *pradeept at hrgiants.com* or call me at *510 870 2315. PDT* Description: Join our agile team of Ruby on Rails developers building wireless home automation services in Golden, Colorado. We''re developing with leading-edge technologies for a global market, and are looking for bright, capable web

Is there any good alternative to resque to management of queue considering cpu memory and usage to increase or decrease background jobs ? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send

I''m using Resque to send Devise emails. To do so I set: devise.rb config.mailer = "Mailers::Devise::DeviseMailer" But I have 2 devise models -- User and Client. I want to send different devise mailer templates for each. devise.rb says "The first four configuration values can also be set straight in your models.", and config.mailer is one of those first four, but

hey everyone i want to send mails by scheduling the time dynamically.lets say in a single table i have all the employee logs who came at different timings.they are from different locations and departments. i want to send mails to different mails ids according to there location to there HR. can i do this with cron job. thanks in advance -- You received this message because you are subscribed to

In pre Rails 3 world I was using ar_sendmail to queue up emails. Then I would setup a cron job every few minutes to deliver the emails. But that doesn''t work perfectly in Rails 3. What is the best way to deliver emails in production environment in Rails 3? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

http://stackoverflow.com/questions/16770090/storing-rails-controller-callback-data-in-session The idea is: - Perform some time consuming action in background. - Have the results from that action be propagated back to the controller using a callback. - Store the result in an in memory session store. - Have the result in session be used and available from that point onward.

I need advice about What is the best practice to scale RoR project ? My current stack is: - Ruby 1.9.3 - RoR 3.2.8 - Redis DB for caching and some hot data - PostgreSQL - Resque for background jobs I am expecting a highload for my project for several month. And I need to change my architecture. Primarily, I want to change my backend architecture. I read about highload

Hi, I have a Rails 3.2 app. There is a specific request that takes a long time to execute. The context is, the user uploads a pdf, and then we have some processing through carrierwave + rmagick that generate a jpeg from the first page of the document. Everything works in dev mode using both webrick and thin. The problem happens on the prod environment with Nginx + Passenger. The request takes a

Hi, I''m wondering why SIGINT and SIGTERM both were chosen for the quick shutdown? I agree with SIGINT but not with SIGTERM. A lot of unix tools send SIGTERM as default (kill, runit among some) and it seems to be the standard way of telling a process to quit gracefully but not among Ruby people (there are a few other ruby processes behaving the same way). I just think it''s weird

Hi guys, I must be missing something obvious with pessimistic locking. Here is what I do (Rails 2.3, mySQL): In my Foo model: def test Foo.transaction do lock = UpdateLockForFoo.find_by_foo_id(self.id, :lock => true) sleep 30 end end For each Foo model, I have an UpdateLockForFoo. This "lock" needs to be acquired before doing any changes to Foo. I believe it works,