title: Resque on Heroku cedar stack Worker count still exists after the worker terminate
body: <p>I have successfully run resque on heroku cedar stack and mount the interface on rails.</p>
  
  <p>when I start the worker, Everything works fine. The worker process the job. But When i kill the worker, Resque still think that the worker is available. When I start another worker, it then think there are 2 worker but in fact there is only one running.</p>
  
  <p>I also notice form here <a href="http://devcenter.heroku.com/articles/ps" rel="noreferrer">http://devcenter.heroku.com/articles/ps</a> that heroku send SIGTERM when killing a worker and if that does not terminate then it send SIGKILL.</p>
  
  <p>here is my worker logs</p>
  
  <pre><code>2011-08-11T02:32:45+00:00 heroku[worker.1]: Starting process with command `bundle exec rake resque:work QUEUE=*`
  2011-08-11T02:32:46+00:00 heroku[worker.1]: State changed from starting to up
  2011-08-11T02:33:58+00:00 heroku[worker.1]: State changed from up to stopping
  2011-08-11T02:34:00+00:00 heroku[worker.1]: Stopping process with SIGTERM
  2011-08-11T02:34:09+00:00 heroku[worker.1]: Error R12 (Exit timeout) -&gt; Process failed to exit within 10 seconds of SIGTERM
  2011-08-11T02:34:09+00:00 heroku[worker.1]: Stopping process with SIGKILL
  2011-08-11T02:34:11+00:00 heroku[worker.1]: Process exited
  </code></pre>
  
  <p>I see that my process takes more then 10s to terminate. Is this have anything to do because I load up rails environment on the worker task ?</p>
  
  <p>this is my rake task <code>lib/tasks/resque.rake</code></p>
  
  <pre><code>require "resque/tasks"
  
  task "resque:setup"  =&gt; :environment
  </code></pre>