thr3ads.net - Ironruby core - [Ironruby-core] IronRuby Rack Timeout causing issues at startup [Sep 2009]

If this information is useful, please help other people find it:
Share via:

Martin Smith

2009-Sep-12 09:58 UTC

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hello,

I wanted to let you know I was having all sorts of troubles getting
Rails to start reliably running on IIS6 (though I don''t think IIS6 has
anything to do with it) and I had to increase the script timeout for
the very first load of the application.

I changed HttpHandler to the one i''ve included below.  I think the
locking is right, but has the side effect of possibly a few of the
early scripts getting a longer timeout than expected. That''s probably
ok, but I''m not sure it''s an "enterprise ready"
solution.

What do you guys think?  Source included below.

Thanks,
Martin

--------------- begin --------------------
internal sealed class HttpHandler : IHttpHandler {

        private readonly Stopwatch _watch = new Stopwatch();
        private static bool _isFirstRequest = true; // added this

        public bool IsReusable {
            get { return true; }
        }

        public void ProcessRequest(HttpContext context) {
            lock (this) {
                if (_isFirstRequest) // added this if block
                {
                    context.Server.ScriptTimeout = 600;
                    _isFirstRequest = false;
                }

                Utils.Log("");
                Utils.Log("=== Request started at " +
DateTime.Now.ToString());
                _watch.Reset();
                _watch.Start();

                Handler.IIS.Current.Handle(new Request(new
HttpRequestWrapper(context.Request)),
                                           new Response(new
HttpResponseWrapper(context.Response)));

                _watch.Stop();
                Utils.Log(">>> Request finished (" +
_watch.ElapsedMilliseconds.ToString() + "ms)");
            }
        }
    }

------------- end --------------------------

Jimmy Schementi

2009-Sep-28 17:29 UTC

head link

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

What you''re experiencing should not be anything specific to IIS6; the
first request of a IronRuby-based app is going to take a longer amount of time
because IronRuby.Rack is compiling and running all the non-app code (Camping +
other Ruby libraries, in your case). In other words, it''s like your
starting the server on the first run. IIS7 defaults to 110 seconds for a
timeout, and I assume IIS6 has the same, which should be way more than enough
time to start the app; a basic Rails app takes ~15 seconds to start up on my
machine. How long does your app take to start outside of IIS? There should be no
difference whether your running in IIS or not.
________________________________________
From: ironruby-core-bounces at rubyforge.org [ironruby-core-bounces at
rubyforge.org] on behalf of Martin Smith [martin.smith.jr at gmail.com]
Sent: Saturday, September 12, 2009 2:58 AM
To: ironruby-core at rubyforge.org
Subject: [Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hello,

I wanted to let you know I was having all sorts of troubles getting
Rails to start reliably running on IIS6 (though I don''t think IIS6 has
anything to do with it) and I had to increase the script timeout for
the very first load of the application.

I changed HttpHandler to the one i''ve included below.  I think the
locking is right, but has the side effect of possibly a few of the
early scripts getting a longer timeout than expected. That''s probably
ok, but I''m not sure it''s an "enterprise ready"
solution.

What do you guys think?  Source included below.

Thanks,
Martin

--------------- begin --------------------
internal sealed class HttpHandler : IHttpHandler {

        private readonly Stopwatch _watch = new Stopwatch();
        private static bool _isFirstRequest = true; // added this

        public bool IsReusable {
            get { return true; }
        }

        public void ProcessRequest(HttpContext context) {
            lock (this) {
                if (_isFirstRequest) // added this if block
                {
                    context.Server.ScriptTimeout = 600;
                    _isFirstRequest = false;
                }

                Utils.Log("");
                Utils.Log("=== Request started at " +
DateTime.Now.ToString());
                _watch.Reset();
                _watch.Start();

                Handler.IIS.Current.Handle(new Request(new
HttpRequestWrapper(context.Request)),
                                           new Response(new
HttpResponseWrapper(context.Response)));

                _watch.Stop();
                Utils.Log(">>> Request finished (" +
_watch.ElapsedMilliseconds.ToString() + "ms)");
            }
        }
    }

------------- end --------------------------
_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Martin Smith

2009-Sep-29 04:26 UTC

head link

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hi Jimmy,

Rails was taking 5 minutes or so to start up on my Amazon Web Services
machine.  Actually, I was having a ton of troubles getting things all
configured and as soon as I addressed one issue, two more would come
up.  I eventually had to abandon IronRuby for hosting my app.

There were a couple more issues I ran into, but you''re right... on my
dev machine, WEBrick started up much more quickly.

Not sure what the problem was.

Thanks,
Martin

On Mon, Sep 28, 2009 at 10:29 AM, Jimmy Schementi
<Jimmy.Schementi at microsoft.com> wrote:> What you''re experiencing should not be anything specific to IIS6;
the first request of a IronRuby-based app is going to take a longer amount of
time because IronRuby.Rack is compiling and running all the non-app code
(Camping + other Ruby libraries, in your case). In other words, it''s
like your starting the server on the first run. IIS7 defaults to 110 seconds for
a timeout, and I assume IIS6 has the same, which should be way more than enough
time to start the app; a basic Rails app takes ~15 seconds to start up on my
machine. How long does your app take to start outside of IIS? There should be no
difference whether your running in IIS or not.
> ________________________________________
> From: ironruby-core-bounces at rubyforge.org [ironruby-core-bounces at
rubyforge.org] on behalf of Martin Smith [martin.smith.jr at gmail.com]
> Sent: Saturday, September 12, 2009 2:58 AM
> To: ironruby-core at rubyforge.org
> Subject: [Ironruby-core] IronRuby Rack Timeout causing issues at startup
>
> Hello,
>
> I wanted to let you know I was having all sorts of troubles getting
> Rails to start reliably running on IIS6 (though I don''t think IIS6
has
> anything to do with it) and I had to increase the script timeout for
> the very first load of the application.
>
> I changed HttpHandler to the one i''ve included below. ?I think the
> locking is right, but has the side effect of possibly a few of the
> early scripts getting a longer timeout than expected. That''s
probably
> ok, but I''m not sure it''s an "enterprise ready"
solution.
>
> What do you guys think? ?Source included below.
>
> Thanks,
> Martin
>
> --------------- begin --------------------
> internal sealed class HttpHandler : IHttpHandler {
>
> ? ? ? ?private readonly Stopwatch _watch = new Stopwatch();
> ? ? ? ?private static bool _isFirstRequest = true; // added this
>
> ? ? ? ?public bool IsReusable {
> ? ? ? ? ? ?get { return true; }
> ? ? ? ?}
>
> ? ? ? ?public void ProcessRequest(HttpContext context) {
> ? ? ? ? ? ?lock (this) {
> ? ? ? ? ? ? ? ?if (_isFirstRequest) // added this if block
> ? ? ? ? ? ? ? ?{
> ? ? ? ? ? ? ? ? ? ?context.Server.ScriptTimeout = 600;
> ? ? ? ? ? ? ? ? ? ?_isFirstRequest = false;
> ? ? ? ? ? ? ? ?}
>
> ? ? ? ? ? ? ? ?Utils.Log("");
> ? ? ? ? ? ? ? ?Utils.Log("=== Request started at " +
DateTime.Now.ToString());
> ? ? ? ? ? ? ? ?_watch.Reset();
> ? ? ? ? ? ? ? ?_watch.Start();
>
> ? ? ? ? ? ? ? ?Handler.IIS.Current.Handle(new Request(new
> HttpRequestWrapper(context.Request)),
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? new Response(new
> HttpResponseWrapper(context.Response)));
>
> ? ? ? ? ? ? ? ?_watch.Stop();
> ? ? ? ? ? ? ? ?Utils.Log(">>> Request finished (" +
> _watch.ElapsedMilliseconds.ToString() + "ms)");
> ? ? ? ? ? ?}
> ? ? ? ?}
> ? ?}
>
> ------------- end --------------------------
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>

Tomas Matousek

2009-Sep-29 06:49 UTC

head link

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

Any chance you''re running with "Debug" mode on? I
can''t think of why it would take 5 minutes if not.  Could you describe
the issues you''re experiencing so that we can work on fixing them?

Thanks,
Tomas

-----Original Message-----
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at
rubyforge.org] On Behalf Of Martin Smith
Sent: Monday, September 28, 2009 9:26 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hi Jimmy,

Rails was taking 5 minutes or so to start up on my Amazon Web Services machine. 
Actually, I was having a ton of troubles getting things all configured and as
soon as I addressed one issue, two more would come up.  I eventually had to
abandon IronRuby for hosting my app.

There were a couple more issues I ran into, but you''re right... on my
dev machine, WEBrick started up much more quickly.

Not sure what the problem was.

Thanks,
Martin

On Mon, Sep 28, 2009 at 10:29 AM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com> wrote:> What you''re experiencing should not be anything specific to IIS6;
the first request of a IronRuby-based app is going to take a longer amount of
time because IronRuby.Rack is compiling and running all the non-app code
(Camping + other Ruby libraries, in your case). In other words, it''s
like your starting the server on the first run. IIS7 defaults to 110 seconds for
a timeout, and I assume IIS6 has the same, which should be way more than enough
time to start the app; a basic Rails app takes ~15 seconds to start up on my
machine. How long does your app take to start outside of IIS? There should be no
difference whether your running in IIS or not.
> ________________________________________
> From: ironruby-core-bounces at rubyforge.org 
> [ironruby-core-bounces at rubyforge.org] on behalf of Martin Smith 
> [martin.smith.jr at gmail.com]
> Sent: Saturday, September 12, 2009 2:58 AM
> To: ironruby-core at rubyforge.org
> Subject: [Ironruby-core] IronRuby Rack Timeout causing issues at 
> startup
>
> Hello,
>
> I wanted to let you know I was having all sorts of troubles getting 
> Rails to start reliably running on IIS6 (though I don''t think IIS6
has
> anything to do with it) and I had to increase the script timeout for 
> the very first load of the application.
>
> I changed HttpHandler to the one i''ve included below. ?I think the
> locking is right, but has the side effect of possibly a few of the 
> early scripts getting a longer timeout than expected. That''s
probably
> ok, but I''m not sure it''s an "enterprise ready"
solution.
>
> What do you guys think? ?Source included below.
>
> Thanks,
> Martin
>
> --------------- begin -------------------- internal sealed class 
> HttpHandler : IHttpHandler {
>
> ? ? ? ?private readonly Stopwatch _watch = new Stopwatch();
> ? ? ? ?private static bool _isFirstRequest = true; // added this
>
> ? ? ? ?public bool IsReusable {
> ? ? ? ? ? ?get { return true; }
> ? ? ? ?}
>
> ? ? ? ?public void ProcessRequest(HttpContext context) {
> ? ? ? ? ? ?lock (this) {
> ? ? ? ? ? ? ? ?if (_isFirstRequest) // added this if block
> ? ? ? ? ? ? ? ?{
> ? ? ? ? ? ? ? ? ? ?context.Server.ScriptTimeout = 600;
> ? ? ? ? ? ? ? ? ? ?_isFirstRequest = false;
> ? ? ? ? ? ? ? ?}
>
> ? ? ? ? ? ? ? ?Utils.Log("");
> ? ? ? ? ? ? ? ?Utils.Log("=== Request started at " + 
> DateTime.Now.ToString());
> ? ? ? ? ? ? ? ?_watch.Reset();
> ? ? ? ? ? ? ? ?_watch.Start();
>
> ? ? ? ? ? ? ? ?Handler.IIS.Current.Handle(new Request(new 
> HttpRequestWrapper(context.Request)),
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? new Response(new 
> HttpResponseWrapper(context.Response)));
>
> ? ? ? ? ? ? ? ?_watch.Stop();
> ? ? ? ? ? ? ? ?Utils.Log(">>> Request finished (" +
> _watch.ElapsedMilliseconds.ToString() + "ms)");
> ? ? ? ? ? ?}
> ? ? ? ?}
> ? ?}
>
> ------------- end -------------------------- 
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Martin Smith

2009-Sep-29 17:13 UTC

head link

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hi Tomas,

Thanks for responding.  It was a couple weeks ago, so I can really
only discuss things from memory.  To be honest, even the simple
IronRuby.Rack test app would take a minute or two to load.

I tried to add Rails'' DB session store, and, oddly, it kept switching
two of the column names so it would be trying to insert a long binary
stream into a short column and giving me the "data would be truncated"
error

The biggest problem is that the worker process would keep dying with
no explanation or error, and i would just get an error in the
Application log that the worker process died.

I''ve since tried running ASP.NET MVC on the same server without issue,
so I''m pretty sure this was related to IronRuby somehow.  I''m
sorry I
can''t be more helpful.  I was under a deadline and ended up having to
re-implement the site on ASP.NET MVC so I couldn''t be as helpful as I
would have liked.  If I get the chance, I''ll try and reconfigure it
again to see if I can track down some of the errors I was seeing.

Thanks,
Martin



On Mon, Sep 28, 2009 at 11:49 PM, Tomas Matousek
<Tomas.Matousek at microsoft.com> wrote:> Any chance you''re running with "Debug" mode on? I
can''t think of why it would take 5 minutes if not. ?Could you describe
the issues you''re experiencing so that we can work on fixing them?
>
> Thanks,
> Tomas
>
> -----Original Message-----
> From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces
at rubyforge.org] On Behalf Of Martin Smith
> Sent: Monday, September 28, 2009 9:26 PM
> To: ironruby-core at rubyforge.org
> Subject: Re: [Ironruby-core] IronRuby Rack Timeout causing issues at
startup
>
> Hi Jimmy,
>
> Rails was taking 5 minutes or so to start up on my Amazon Web Services
machine. ?Actually, I was having a ton of troubles getting things all configured
and as soon as I addressed one issue, two more would come up. ?I eventually had
to abandon IronRuby for hosting my app.
>
> There were a couple more issues I ran into, but you''re right... on
my dev machine, WEBrick started up much more quickly.
>
> Not sure what the problem was.
>
> Thanks,
> Martin
>
> On Mon, Sep 28, 2009 at 10:29 AM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com> wrote:
>> What you''re experiencing should not be anything specific to
IIS6; the first request of a IronRuby-based app is going to take a longer amount
of time because IronRuby.Rack is compiling and running all the non-app code
(Camping + other Ruby libraries, in your case). In other words, it''s
like your starting the server on the first run. IIS7 defaults to 110 seconds for
a timeout, and I assume IIS6 has the same, which should be way more than enough
time to start the app; a basic Rails app takes ~15 seconds to start up on my
machine. How long does your app take to start outside of IIS? There should be no
difference whether your running in IIS or not.
>> ________________________________________
>> From: ironruby-core-bounces at rubyforge.org
>> [ironruby-core-bounces at rubyforge.org] on behalf of Martin Smith
>> [martin.smith.jr at gmail.com]
>> Sent: Saturday, September 12, 2009 2:58 AM
>> To: ironruby-core at rubyforge.org
>> Subject: [Ironruby-core] IronRuby Rack Timeout causing issues at
>> startup
>>
>> Hello,
>>
>> I wanted to let you know I was having all sorts of troubles getting
>> Rails to start reliably running on IIS6 (though I don''t think
IIS6 has
>> anything to do with it) and I had to increase the script timeout for
>> the very first load of the application.
>>
>> I changed HttpHandler to the one i''ve included below. ?I think
the
>> locking is right, but has the side effect of possibly a few of the
>> early scripts getting a longer timeout than expected. That''s
probably
>> ok, but I''m not sure it''s an "enterprise
ready" solution.
>>
>> What do you guys think? ?Source included below.
>>
>> Thanks,
>> Martin
>>
>> --------------- begin -------------------- internal sealed class
>> HttpHandler : IHttpHandler {
>>
>> ? ? ? ?private readonly Stopwatch _watch = new Stopwatch();
>> ? ? ? ?private static bool _isFirstRequest = true; // added this
>>
>> ? ? ? ?public bool IsReusable {
>> ? ? ? ? ? ?get { return true; }
>> ? ? ? ?}
>>
>> ? ? ? ?public void ProcessRequest(HttpContext context) {
>> ? ? ? ? ? ?lock (this) {
>> ? ? ? ? ? ? ? ?if (_isFirstRequest) // added this if block
>> ? ? ? ? ? ? ? ?{
>> ? ? ? ? ? ? ? ? ? ?context.Server.ScriptTimeout = 600;
>> ? ? ? ? ? ? ? ? ? ?_isFirstRequest = false;
>> ? ? ? ? ? ? ? ?}
>>
>> ? ? ? ? ? ? ? ?Utils.Log("");
>> ? ? ? ? ? ? ? ?Utils.Log("=== Request started at " +
>> DateTime.Now.ToString());
>> ? ? ? ? ? ? ? ?_watch.Reset();
>> ? ? ? ? ? ? ? ?_watch.Start();
>>
>> ? ? ? ? ? ? ? ?Handler.IIS.Current.Handle(new Request(new
>> HttpRequestWrapper(context.Request)),
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? new Response(new
>> HttpResponseWrapper(context.Response)));
>>
>> ? ? ? ? ? ? ? ?_watch.Stop();
>> ? ? ? ? ? ? ? ?Utils.Log(">>> Request finished (" +
>> _watch.ElapsedMilliseconds.ToString() + "ms)");
>> ? ? ? ? ? ?}
>> ? ? ? ?}
>> ? ?}
>>
>> ------------- end --------------------------
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>

Jimmy Schementi

2009-Sep-29 19:42 UTC

head link

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

Martin,

It''s unfortunate that you had such trouble getting IronRuby to work on
AWS. ASP.NET MVC is the right choice for now, as I''m still flushing out
bugs with the Rack implementation. Have you seen IronRubyMVC?
http://github.com/casualjim/ironrubymvc. That will let you write ASP.NET MVC
applications with Ruby, and the polygot in me likes this approach much more;
have a static compiled language be your framework, and a scripting language be
your application code. That being said, running the existing Ruby web frameworks
should work as good or better than MRI on IronRuby (at least, that''s
the goal), so tracking down issues like this is of most importance.

Thanks for offering to track down these issues! Also make sure to see whether or
not the same issues occur locally; AWS may have some restrictions I
didn''t anticipate. If you''d like to debug this together, via
live meeting, skype, or whatever communication tool of your choice, let me know
... I''m more than happy to help out.

~Jimmy
________________________________________
From: ironruby-core-bounces at rubyforge.org [ironruby-core-bounces at
rubyforge.org] on behalf of Martin Smith [martin.smith.jr at gmail.com]
Sent: Tuesday, September 29, 2009 10:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] IronRuby Rack Timeout causing issues at startup

Hi Tomas,

Thanks for responding.  It was a couple weeks ago, so I can really
only discuss things from memory.  To be honest, even the simple
IronRuby.Rack test app would take a minute or two to load.

I tried to add Rails'' DB session store, and, oddly, it kept switching
two of the column names so it would be trying to insert a long binary
stream into a short column and giving me the "data would be truncated"
error

The biggest problem is that the worker process would keep dying with
no explanation or error, and i would just get an error in the
Application log that the worker process died.

I''ve since tried running ASP.NET MVC on the same server without issue,
so I''m pretty sure this was related to IronRuby somehow.  I''m
sorry I
can''t be more helpful.  I was under a deadline and ended up having to
re-implement the site on ASP.NET MVC so I couldn''t be as helpful as I
would have liked.  If I get the chance, I''ll try and reconfigure it
again to see if I can track down some of the errors I was seeing.

Thanks,
Martin



On Mon, Sep 28, 2009 at 11:49 PM, Tomas Matousek
<Tomas.Matousek at microsoft.com> wrote:> Any chance you''re running with "Debug" mode on? I
can''t think of why it would take 5 minutes if not.  Could you describe
the issues you''re experiencing so that we can work on fixing them?
>
> Thanks,
> Tomas
>
> -----Original Message-----
> From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces
at rubyforge.org] On Behalf Of Martin Smith
> Sent: Monday, September 28, 2009 9:26 PM
> To: ironruby-core at rubyforge.org
> Subject: Re: [Ironruby-core] IronRuby Rack Timeout causing issues at
startup
>
> Hi Jimmy,
>
> Rails was taking 5 minutes or so to start up on my Amazon Web Services
machine.  Actually, I was having a ton of troubles getting things all configured
and as soon as I addressed one issue, two more would come up.  I eventually had
to abandon IronRuby for hosting my app.
>
> There were a couple more issues I ran into, but you''re right... on
my dev machine, WEBrick started up much more quickly.
>
> Not sure what the problem was.
>
> Thanks,
> Martin
>
> On Mon, Sep 28, 2009 at 10:29 AM, Jimmy Schementi <Jimmy.Schementi at
microsoft.com> wrote:
>> What you''re experiencing should not be anything specific to
IIS6; the first request of a IronRuby-based app is going to take a longer amount
of time because IronRuby.Rack is compiling and running all the non-app code
(Camping + other Ruby libraries, in your case). In other words, it''s
like your starting the server on the first run. IIS7 defaults to 110 seconds for
a timeout, and I assume IIS6 has the same, which should be way more than enough
time to start the app; a basic Rails app takes ~15 seconds to start up on my
machine. How long does your app take to start outside of IIS? There should be no
difference whether your running in IIS or not.
>> ________________________________________
>> From: ironruby-core-bounces at rubyforge.org
>> [ironruby-core-bounces at rubyforge.org] on behalf of Martin Smith
>> [martin.smith.jr at gmail.com]
>> Sent: Saturday, September 12, 2009 2:58 AM
>> To: ironruby-core at rubyforge.org
>> Subject: [Ironruby-core] IronRuby Rack Timeout causing issues at
>> startup
>>
>> Hello,
>>
>> I wanted to let you know I was having all sorts of troubles getting
>> Rails to start reliably running on IIS6 (though I don''t think
IIS6 has
>> anything to do with it) and I had to increase the script timeout for
>> the very first load of the application.
>>
>> I changed HttpHandler to the one i''ve included below.  I think
the
>> locking is right, but has the side effect of possibly a few of the
>> early scripts getting a longer timeout than expected. That''s
probably
>> ok, but I''m not sure it''s an "enterprise
ready" solution.
>>
>> What do you guys think?  Source included below.
>>
>> Thanks,
>> Martin
>>
>> --------------- begin -------------------- internal sealed class
>> HttpHandler : IHttpHandler {
>>
>>        private readonly Stopwatch _watch = new Stopwatch();
>>        private static bool _isFirstRequest = true; // added this
>>
>>        public bool IsReusable {
>>            get { return true; }
>>        }
>>
>>        public void ProcessRequest(HttpContext context) {
>>            lock (this) {
>>                if (_isFirstRequest) // added this if block
>>                {
>>                    context.Server.ScriptTimeout = 600;
>>                    _isFirstRequest = false;
>>                }
>>
>>                Utils.Log("");
>>                Utils.Log("=== Request started at " +
>> DateTime.Now.ToString());
>>                _watch.Reset();
>>                _watch.Start();
>>
>>                Handler.IIS.Current.Handle(new Request(new
>> HttpRequestWrapper(context.Request)),
>>                                           new Response(new
>> HttpResponseWrapper(context.Response)));
>>
>>                _watch.Stop();
>>                Utils.Log(">>> Request finished (" +
>> _watch.ElapsedMilliseconds.ToString() + "ms)");
>>            }
>>        }
>>    }
>>
>> ------------- end --------------------------
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>_______________________________________________
Ironruby-core mailing list
Ironruby-core at rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Ironruby core - Sep 2009 - IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup

[Ironruby-core] IronRuby Rack Timeout causing issues at startup