From: Luis Lavena <luislavena@...>
Date: 2008-12-30T11:39:36+09:00
Subject: Re: Bug In Ruby 1.8.6-26

On Dec 29, 4:27 pm, Opt Opt <jp0...@gmail.com> wrote:
> Luis Lavena wrote:
> > On Dec 29, 3:36 pm, Opt Opt <jp0...@gmail.com> wrote:
> >> Application Name: ruby.exe
> >> Additional Information 2: 512258a507002ee6a0cd148c12c4d72e
>
> >> This application has requested the Runtime to terminate it in an unusual
> >> way.
> >> Please contact the application's support team for more information.
> >> --
> >> Posted viahttp://www.ruby-forum.com/.
>
> > Can you provide more information about your environment?
>
> > Looks like you're using Rails, which version?
>
> > Also, you're running Webrick or Mongrel?
>
> > Are you refreshing too quick and not letting the connection and
> > rendering complete? that could affect code execution too.
>
> Rails version 2.2.2. Webrick development server. Windows Vista 32-bit.
> And keep in mind everything is being done from the eclipse environment.

Two things:

1) Can you use mongrel instead?

gem install mongrel

Then use mongrel_rails:

mongrel_rails start

Webrick is know to have problems, but none of I'm aware related to
Timeout.

2) Try running form the command line and try to reproduce it.

Maybe is not related to Webrick or Ruby itself, but something that
your Rails application is doing on the requests (like using puts to
log debug information).

Also, use another URL (controller and/or action) and see if the
problems happens again.

HTH,
--
Luis Lavena