Repeated Race Conditions in Rails 3.0

I’m using “rails s” to test. I have a simple search controller, with
an index method that I call with different parameters that let me
drill down in a result set.

I have a link_to that is calling the exact same search_url method in
the view, but with an additional parameter. The link is being
generated just fine. But when I click on that link, the following
happens:

  1. The ruby process jumps to 100% CPU utilization
  2. Nothing is written to the console. Not even the request.
  3. Ctrl-C won’t quit, the thing is hung.

I can’t troubleshoot what I can’t see. Is there somewhere else I can
get a stack trace from in order to figure out why my little app is
struggling so badly with this simple request?

On Wed, Sep 29, 2010 at 12:54 PM, AK [email protected]
wrote:

  1. Nothing is written to the console. Not even the request.
  2. Ctrl-C won’t quit, the thing is hung.

I can’t troubleshoot what I can’t see. Is there somewhere else I can
get a stack trace from in order to figure out why my little app is
struggling so badly with this simple request?

In development you typically run a single Ruby that can only handle
one request at a time. This is normal. Run your app under passenger
(or something similar) if you want more than one request at a time be
fulfilled.


Greg D.
destiney.com | gregdonald.com

On Wednesday 29 September 2010, AK wrote:

  1. The ruby process jumps to 100% CPU utilization
  2. Nothing is written to the console. Not even the request.
  3. Ctrl-C won’t quit, the thing is hung.

I can’t troubleshoot what I can’t see. Is there somewhere else I can
get a stack trace from in order to figure out why my little app is
struggling so badly with this simple request?

Insert a debugger call in the appropriate place, presumably the
controller action, and start your server with rails s -d.

Michael


Michael S.
mailto:[email protected]
http://www.schuerig.de/michael/