Whether that will work or not depends on what Apache MPM you are using
and how you have it configured.
It also depends on what 'other endpts' is. Are these with App2, or
other external sites?
So, what MPM are you using. See:
http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation#Apache_Build_Information
for how to work that out.
Also, what are the MPM settings being used. Ie., what do you have for:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 1
MinSpareServers 1
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
If the Apache MPM settings are such that there are limited
processes/threads for handling requests, then doing loopback HTTP
request against the same server will deadlock or stall when done when
all processes/threads are busy handling requests, or busy handing keep
alive connections.
Why do you need to do a HTTP get back against other application hosted
on same Apache?
Graham
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response
to track calls into application and subsequent exit. See if the sub
call actually makes it to the second WSGI application.
One possibility is that both applications need to acquire a lock of
some sort on a resource and when making the call to the second, the
first isn't releasing that resource so when second gets request it
blocks waiting for resource to be released, but that will never happen
as first application will only do that when second returns, which it
will not be because it is blocked.
Graham
> --
> You received this message because you are subscribed to the Google Groups "modwsgi" group.
> To post to this group, send email to mod...@googlegroups.com.
> To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
>
>