Application always unresponsive overnight

Hi,

I set up my application on Linux (Suse), running MySQL (which sits on a
different server) and Webrick. It works fine. However, every morning
when I come back to my desk, the application gets unresponsive. If I
simply access http://host:3000 http://host:3000/ I can see the rails
greeting page (that means Webrick is running fine right?), but if I
access any of pages in the application, the browser just loads forever.
It doesn’t say page not found or anything, but keeps connecting until
timed out. (If I just kill the process, and restart script/server -d,
the page loads fine again.)

I thought it might have something to do with MySQL’s connection, so I
wrote a controller that simply has render_text … when I access
http://host:3000/test, it doesn’t load either. So does that mean it’s
not MySQL’s problem?

So then I suspected it might still be a problem with Webrick. However,
from reading the mailing list, people seem to be able to run Webrick
continuously for days with no problem…

I don’t really know where to start debugging this problem. So any tips
would be appreciated.

Thanks in advance.

Nina Ye
Sr. Software Engineer
SUCCESSFACTORS
Tel: 650-645-2062
Fax: 650-645-2377

I set up my application on Linux (Suse), running MySQL (which sits on a
different server) and Webrick. It works fine. However, every morning
when I come back to my desk, the application gets unresponsive. If I

hi, nina…

i am having alot of the same problems… but here’s something that has
worked for me in some instances…

http://www.ruby-forum.com/topic/70825#96966

On Jul 13, 2006, at 11:41 AM, Nina Ye wrote:

I set up my application on Linux (Suse), running MySQL (which sits
on a different server) and Webrick. It works fine. However, every
morning when I come back to my desk, the application gets
unresponsive. If I simply access http://host:3000 I can see the
rails greeting page (that means Webrick is running fine right?),
but if I access any of pages in the application, the browser just
loads forever. It doesn?t say page not found or anything, but
keeps connecting until timed out. (If I just kill the process, and
restart script/server ?d, the page loads fine again.)
This sure sounds like MySQL timeout.

I thought it might have something to do with MySQL?s connection, so
I wrote a controller that simply has render_text … when I access
http://host:3000/test, it doesn?t load either. So does that mean
it?s not MySQL?s problem?
You beat me too it! :slight_smile:

No, it could still be MySQL if you’re using ActiveRecordStore for
your sessions.


– Tom M.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs