Apache WSGI Timeouts After 5 Minutes / How to Set the Maximum Number of WSGI Processes
up vote
0
down vote
favorite
I am using Apache and WSGI under Linux to spawn Python processes that run R reports.
It works wonderfully if my Python processes finish in less than 5 minutes. I can stack them up no issue. If reports run longer, I get a timeout on the web client side. What am I doing wrong? How do you set a timeout maximum greater? I'm assuming that 5 minutes is the default.
One additional question - How can I regulate how many Python processes I can spawn under Apache at one time? I know part of that answer is regulated by the number of web requests from the client end.
Any help is greatly appreciated.
Thanks,
Lou
python apache mod-wsgi wsgi
asked Nov 10 at 14:11
user7945126
143
add a comment |
up vote
0
down vote
favorite
I am using Apache and WSGI under Linux to spawn Python processes that run R reports.
It works wonderfully if my Python processes finish in less than 5 minutes. I can stack them up no issue. If reports run longer, I get a timeout on the web client side. What am I doing wrong? How do you set a timeout maximum greater? I'm assuming that 5 minutes is the default.
One additional question - How can I regulate how many Python processes I can spawn under Apache at one time? I know part of that answer is regulated by the number of web requests from the client end.
Any help is greatly appreciated.
Thanks,
Lou
python apache mod-wsgi wsgi
asked Nov 10 at 14:11
user7945126
143
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using Apache and WSGI under Linux to spawn Python processes that run R reports.
It works wonderfully if my Python processes finish in less than 5 minutes. I can stack them up no issue. If reports run longer, I get a timeout on the web client side. What am I doing wrong? How do you set a timeout maximum greater? I'm assuming that 5 minutes is the default.
One additional question - How can I regulate how many Python processes I can spawn under Apache at one time? I know part of that answer is regulated by the number of web requests from the client end.
Any help is greatly appreciated.
Thanks,
Lou
python apache mod-wsgi wsgi
asked Nov 10 at 14:11
user7945126
143
I am using Apache and WSGI under Linux to spawn Python processes that run R reports.
It works wonderfully if my Python processes finish in less than 5 minutes. I can stack them up no issue. If reports run longer, I get a timeout on the web client side. What am I doing wrong? How do you set a timeout maximum greater? I'm assuming that 5 minutes is the default.
One additional question - How can I regulate how many Python processes I can spawn under Apache at one time? I know part of that answer is regulated by the number of web requests from the client end.
Any help is greatly appreciated.
Thanks,
Lou
python apache mod-wsgi wsgi
python apache mod-wsgi wsgi
asked Nov 10 at 14:11
user7945126
143
asked Nov 10 at 14:11
user7945126
143
asked Nov 10 at 14:11
user7945126
143
asked Nov 10 at 14:11
user7945126
143
asked Nov 10 at 14:11
user7945126
143
143
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18
add a comment |
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239801%2fapache-wsgi-timeouts-after-5-minutes-how-to-set-the-maximum-number-of-wsgi-pro%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Advice: A general way to get around long running processes is to have the process indicate when it is completed, and the client repeatedly check for the "indicator flag" separately via ajax.
– Paritosh Singh
Nov 10 at 14:18