Mailing List Archive: Cherokee: dev

Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI

Index | Next | Previous | View Threaded

codesite-noreply at google

Jun 20, 2009, 9:40 AM

Post #1 of 14 (1093 views)
Permalink

Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI

Status: New
Owner: ----

New issue 499 by superman.jason: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

What steps will reproduce the problem?
1. Access a php page that calls another process that takes a long time to
complete. (Example, a gallery script that calls GD or ImageMagick to
process an image, or another script that parses a large number of, for
instance customer names, from a MySQL database.

What is the expected output? What do you see instead?
Delayed page rendering is expected. Seeing "500 Server Error", or "504
Gateway Timeout", or "Page Load Error: Connection Interrupted".

What version of the product are you using? On what operating system?
0.99.17 on FreeBSD 7.2-RELEASE-p1

Please provide any additional information below.

To quote Alvaro's request to file this "bug.": "[We could] improve the
timeout support so different values could be defined for the client-server
connection and the server-fastcgi. In that way, you could set a higher
value for the FastCGI connection while the client-server timeout value
remains the same."

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 21, 2009, 6:23 AM

Post #2 of 14 (918 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Updates:
Status: WaitingQA
Owner: alobbs
Labels: Type-Enhancement Priority-High OpSys-All Component-Logic

Comment #1 on issue 499 by alobbs: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

With the following php file,
========
<?php
sleep (25);
phpinfo();
?>
========

and the default configuration; the result is,
========
> GET /slow.php HTTP/1.1
> Host: localhost

< HTTP/1.0 504 Gateway Timeout
========

Now, if you go to cherokee-admin, and set a timeout of -let's say- 40
seconds, the
behavior changes completely:

Virtual Servers -> default -> Behavior -> Extension PHP -> Time -> Timeout

========
> GET /slow.php HTTP/1.1
> Host: localhost

< HTTP/1.1 200 OK
========

This is a new feature of the upcoming Cherokee 0.99.30 release.

All sort of feedback about this new feature would be greatly appreciated.
Snapshot
tarballs can be found at:

http://www.cherokee-project.com/download/trunk/

Thanks for logging the RFE!

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 3:42 AM

Post #3 of 14 (905 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #2 on issue 499 by skarcha: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

I like the implementation, and seems that works like a charm on my
tests... ;)

Thanks! ;)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 3:57 AM

Post #4 of 14 (907 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Updates:
Status: Verified

Comment #3 on issue 499 by alobbs: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Actually, I had to rewrite the same thing twice. At the beginning I thought
it was a
much tougher feature to implement, and that drove me to choose the wrong
approach.

It's been also working alright for me, so I'm closing this bug now.

@skarcha: Thanks for the feedback.
@superman.jason: Thanks for logging the RFE!

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 7:03 AM

Post #5 of 14 (906 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #4 on issue 499 by superman.jason: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Hi Alvaro,

You are welcome, and I'm glad this is getting fixed. It's been a
show-stopper for my
applications. I may switch back to using Cherokee in production!

I found with this new setting, almost all the aforementioned issues went
away,
however I did still find this one issue. Although it turned out to be an
issue with
Suhosin encrypted sessions, when I used Lighty with FastCGI, the page in
question
would just take a long time to load, but would eventually finish, but
without some
information that would normally be displayed because of the encrypted
session.
However, Cherokee on the same page, takes a long time, and then brings up a
browser
error page, instead of finishing the page with incomplete information.

I don't know the implications as far as code, memory usage, etc, but in
this one
instance I wish Cherokee was like Lighttpd. I have noticed the same problem
with
other Web Servers that take the "hands off" approach to PHP, such as nginx
and
Hiawatha...

Anyway, I still think Cherokee is a GREAT web server, and the configuration
GUI is
excellent! I also appreciate how you are very active and responsive to
questions and
issues, so keep up the great work!

Thanks,
Jason

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 7:08 AM

Post #6 of 14 (918 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #5 on issue 499 by ste...@konink.de: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Separate bug please. Next to that I would vote a -1 for it.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 8:42 AM

Post #7 of 14 (905 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #6 on issue 499 by superman.jason: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Actually, after some coffee and using more of my brain, I see that with
this new time
setting I can overcome this issue as well! All I need to do is set the
connection
timeout to longer than the max_execution_time as set in php.ini! Still
giving the
browser error page instead of executing the page but with errors is
annoying, but now
I see it can be overcome! I guess this wouldn't really be a bug, so unless
you really
want to post something, I'll leave it be...

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 9:04 AM

Post #8 of 14 (904 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #7 on issue 499 by ste...@konink.de: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Just for the record ;) Isn't it a plain misconfiguration if the script can
execute
longer then the connection timeout :o

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 9:18 AM

Post #9 of 14 (903 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #8 on issue 499 by superman.jason: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Yes, I guess it is! Operator error alert!

Before we couldn't change the PHP connection timeout though, so this new
setting is
great!

I think using...ahem...that other heavyweight web server with
mod_php...perhaps made
me lazy with regard to checking php.ini settings, as it would just work
anyway 99% of
the time. But we won't go there... ;) I'm here because I want a modern,
efficient,
and fast server, and I think this is it!

Thanks,
Jason

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 9:23 AM

Post #10 of 14 (907 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Updates:
Status: WaitingQA

Comment #9 on issue 499 by ste...@konink.de: Define seperate timeout values
for Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

I do see an issue here for our QA team ;) Should we inform the user at this
nice
property that the respectable value in php.ini also has to be set correctly?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 22, 2009, 2:23 PM

Post #11 of 14 (914 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #10 on issue 499 by alobbs: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

If the PHP wizard checked the max_execution_time value in php.ini, it could
set a
reasonable timeout value in Cherokee; and it'd work out of the box.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Dec 1, 2009, 8:59 AM

Post #12 of 14 (855 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #11 on issue 499 by tahers: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

This seems to work perfectly on my tests.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Dec 2, 2009, 10:37 AM

Post #13 of 14 (848 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Comment #12 on issue 499 by mictlan: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

Excelent! This works perfectly on my tests too! :)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Dec 2, 2009, 11:13 AM

Post #14 of 14 (848 views)
Permalink

Re: Issue 499 in cherokee: Define seperate timeout values for Client-Server & Server-FastCGI [In reply to]

Updates:
Status: Fixed

Comment #13 on issue 499 by tahers: Define seperate timeout values for
Client-Server & Server-FastCGI
http://code.google.com/p/cherokee/issues/detail?id=499

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads