> > When I call a page that has a breakpoint, I get the breakpoint > "request" in my script\breakpointer application correctly but! the > problem is that the webpage itself "times out" after half a minute > or so giving me an "Application error" (error 500?) >I''ve had that problem before--but, unfortunately, all I can offer is emotional support. It went away after I upgraded to Tiger, and so I don''t know where to even start looking for the cause. Duane Johnson (canadaduane)
I have a problem with breakpoints. When I call a page that has a breakpoint, I get the breakpoint "request" in my script\breakpointer application correctly but! the problem is that the webpage itself "times out" after half a minute or so giving me an "Application error" (error 500?) I tried setting: RAILS_ENV = ENV[''RAILS_ENV''] || ''development -idle-timeout 999999'' in enviroment.rb but to no avail Any ideas? Thanks, Rob
> When I call a page that has a breakpoint, I get the breakpoint > "request" in my script\breakpointer application correctly but! the > problem is that the webpage itself "times out" after half a minute > or so giving me an "Application error" (error 500?)That''s Apache giving up on script thinking that it died. You can increase the timeout number. If you use FCGI, you need to use - timeout -- that can be set to something like 300 or whatever. -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Duane Johnson wrote:> I''ve had that problem before--but, unfortunately, all I can offer is > emotional support. It went away after I upgraded to Tiger, and so I > don''t know where to even start looking for the cause. >Haha, thanks ;) I''m on Windows. I''ll upgrade to Apple =D soon enough though, so that should do it. Cheers, Rob
David Heinemeier Hansson wrote:> That''s Apache giving up on script thinking that it died. You can > increase the timeout number. If you use FCGI, you need to use - > timeout -- that can be set to something like 300 or whatever.Thanks for the hint. I put the line: FastCgiConfig -idle-timeout 320 into my httpd.conf and now it works Cheers :) Rob