Forum: Ruby on Rails cannot kill infinite loop. please help

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
isabelle (Guest)
on 2006-04-28 18:36
an error in my rails code caused the framework to send an infinite
number of SQL calls to the database. I killed the webrick server,
restarted postgres, deleted the /tmp file in my rails application,
deleted the bad code, restarted firefox, restarted the webrick server.

All to no avail.

As soon as I try loading my application, the infinite recursion starts
again.

I can no longer work. This is so bad I can't tell you how maddening it
is.

any help extremely appreciated.

Isabelle
isabelle (Guest)
on 2006-04-28 19:29
how do I kill a rails thread that sends the same recursing SQL statement
whenever the webrick server is started?

what are all the files I should look for?

I rebooted by machine running linux Fedora Core, emptied my browser
cache, restarted my browser.

I have removed all the rails code that caused the infinite loop. I
restarted webrick and when I load the application, the endless SQL calls
start again:

  Keyword Load (0.004687)   SELECT * FROM keywords WHERE (keywords.id =
949) LIMIT 1
  Keyword Load (0.004808)   SELECT * FROM keywords WHERE (keywords.id =
27) LIMIT 1
  Keyword Load (0.004987)   SELECT * FROM keywords WHERE (keywords.id =
241) LIMIT 1
  Keyword Load (0.004666)   SELECT * FROM keywords WHERE (keywords.id =
949) LIMIT 1
  Keyword Load (0.005433)   SELECT * FROM keywords WHERE (keywords.id =
27) LIMIT 1
  Keyword Load (0.005096)   SELECT * FROM keywords WHERE (keywords.id =
241) LIMIT 1
  Keyword Load (0.004721)   SELECT * FROM keywords WHERE (keywords.id =
949) LIMIT 1
  Keyword Load (0.004887)   SELECT * FROM keywords WHERE (keywords.id =
27) LIMIT 1


I am grateful for any hints. Any.
isabelle (Guest)
on 2006-04-28 19:50
solved by deleting all records in the database that gave the error...

friday night syndrome. sigh.
This topic is locked and can not be replied to.