Rails - Jul 2009 - ActionController::RoutingError (No route matches "/say/hello" with {:method=>:get}):

Hello:

I have found a whole lot of posts on this, however, none of them offer
any sort of solution other than restarting the web server, which I
can''t imagine everyone out there developing on Rails is doing.

I am on page 40 of Agile Development with Rails 3rd edition and trying
to get the missing template error to show but until I restart webrick
I only get the following:

Processing ApplicationController#index (for ::1 at 2009-07-31
12:56:22) [GET]

ActionController::RoutingError (No route matches "/say/hello" with
{:method=>:get}):
  /usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service''
  /usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in `run''
  /usr/local/lib/ruby/1.8/webrick/server.rb:173:in `start_thread''
  /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start''
  /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start_thread''
  /usr/local/lib/ruby/1.8/webrick/server.rb:95:in `start''
  /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `each''
  /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `start''
  /usr/local/lib/ruby/1.8/webrick/server.rb:23:in `start''
  /usr/local/lib/ruby/1.8/webrick/server.rb:82:in `start''

Rendering rescues/layout (not_found)

I found this on the Pragmatic errata site for the book:

I''m really not sure what a non-deterministic bug is? Again, I
can''t
believe everyone out there is restarting their web servers after they
create each controller and view, are they?

#32023: I also got the above - When I run it: "Routing Error No route
matches "/say/hello" with {:method=>:get}"

I had to restart mongrel to get the correct browser display.
OS X 10.4.11 with uptodate rails (2.0.2) per pg 35

(Sam says: this is a non-deterministic bug in Rails. DHH is aware)--
rick Strang

On Jul 31, 3:13 pm, Chris <cmi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
>
> I found this on the Pragmatic errata site for the book:
>
> I''m really not sure what a non-deterministic bug is? Again, I
can''t
> believe everyone out there is restarting their web servers after they
> create each controller and view, are they?
Non deterministic means is a fancy way of saying that it happens
randomly. I have seen this at times, but only ever when adding new
controllers (ie adding actions to existing controllers never seems to
do this) and never when the new controller had restful routes
involved. Between those two that''s the vast majority of my changes
covered without a restart

Fred
>
> #32023: I also got the above - When I run it: "Routing Error No route
> matches "/say/hello" with {:method=>:get}"
>
> I had to restart mongrel to get the correct browser display.
> OS X 10.4.11 with uptodate rails (2.0.2) per pg 35
>
> (Sam says: this is a non-deterministic bug in Rails. DHH is aware)--
> rick Strang

Thank you for your reply. I guess I will have to live with it when I
am adding new controllers without "restful routes" (not sure what that
is but I''m about to go look now!).

I guess for someone who was looking for a change from Tomcat and Java
and was really exited about not having to restart his container, this
seemed to be a real show stopper, but if as you say the vast majority
of your changes are covered without a restart then I''ll be back on my
Rails journey after my vacation!

Thanks a million

On Jul 31, 4:47 pm, Frederick Cheung
<frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> On Jul 31, 3:13 pm, Chris
<cmi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
> > I found this on the Pragmatic errata site for the book:
>
> > I''m really not sure what a non-deterministic bug is? Again, I
can''t
> > believe everyone out there is restarting their web servers after they
> > create each controller and view, are they?
>
> Non deterministic means is a fancy way of saying that it happens
> randomly. I have seen this at times, but only ever when adding new
> controllers (ie adding actions to existing controllers never seems to
> do this) and never when the new controller had restful routes
> involved. Between those two that''s the vast majority of my changes
> covered without a restart
>
> Fred
>
>
>
> > #32023: I also got the above - When I run it: "Routing Error No
route
> > matches "/say/hello" with {:method=>:get}"
>
> > I had to restart mongrel to get the correct browser display.
> > OS X 10.4.11 with uptodate rails (2.0.2) per pg 35
>
> > (Sam says: this is a non-deterministic bug in Rails. DHH is aware)--
> > rick Strang