# Application always unresponsive overnight

**URL:** <https://www.ruby-forum.com/t/application-always-unresponsive-overnight/98317>\
**Category:** Rails\
**Created:** [July 13, 2006, 9:59pm UTC](https://www.ruby-forum.com/t/application-always-unresponsive-overnight/98317 "2006-07-13T21:59:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nina\_Ye](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/a698b9/32.png) [@Nina\_Ye](https://www.ruby-forum.com/u/Nina_Ye)\
**Post date:** [July 13, 2006, 9:59pm UTC](https://www.ruby-forum.com/t/application-always-unresponsive-overnight/98317/1 "2006-07-13T21:59:08Z")

</div>

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) [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](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

---

<div class="post-metadata">

**Author:** ![Nina\_Ye](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/a698b9/32.png) [@Nina\_Ye](https://www.ruby-forum.com/u/Nina_Ye)\
**Post date:** [July 13, 2006, 10:13pm UTC](https://www.ruby-forum.com/t/application-always-unresponsive-overnight/98317/2 "2006-07-13T22:13:57Z")

</div>

> 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](http://www.ruby-forum.com/topic/70825#96966)

---

<div class="post-metadata">

**Author:** ![Nina\_Ye](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/a698b9/32.png) [@Nina\_Ye](https://www.ruby-forum.com/u/Nina_Ye)\
**Post date:** [July 13, 2006, 11:27pm UTC](https://www.ruby-forum.com/t/application-always-unresponsive-overnight/98317/3 "2006-07-13T23:27:08Z")

</div>

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](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](http://host:3000/test), it doesn?t load either. So does that mean  
> it?s not MySQL?s problem?  
> You beat me too it! 🙂

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

–  
– Tom M.
