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? -- 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 email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Sep 29, 2010 at 12:54 PM, AK <ak.from.wake.forest-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> 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?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 Donald destiney.com | gregdonald.com -- 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 email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
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 Schuerig mailto:michael-q5aiKMLteq4b1SvskN2V4Q@public.gmane.org http://www.schuerig.de/michael/ -- 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 email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.