title: Rails Async Active Job doesn't execute code, while inline does
body: <p>Does the :async queue adapter actually do anything?</p>
  
  <p>:inline, which is what is default in Rails 4, processes jobs built with ActiveJob, uh... inline, in the current execution thread. Async, shouldn't. It should use the ConnectionPool to not run it in the current thread, and that's ideally what would be happening. It'd run perform outside of the current execution thread.</p>
  
  <p>But nothing executes it.</p>
  
  <p>I've pored through the docs, and the only thing I can fathom is is that :async, unlike :inline, doesn't execute tasks, and expects you to build a system around execution locally. I have to manually perform <code>perform</code> on all jobs in order to get them to execute locally. When I set the adapter to :inline, it works just fine without having to execute.</p>
  
  <p>Is there some configuration issue I'm missing that's preventing async from working correctly (like ActionCable?).</p>
  
  <p>Does it not work if executed from a rake task (or the console?).</p>
  
  <p>It works fine with :sidekiq/:resque, but I don't want to be running these locally all the time. </p>
  
  <p><code>Rails by default comes with an "immediate runner" queuing implementation. That means that each job that has been enqueued will run immediately.</code></p>
  
  <p>This is kind of what's cueing me in there being something wrong. I have jobs that are sitting in a queue somewhere that just don't run. What could be stopping this?</p>