RE: How does Fast CGi know whether the Process is inPro cess or not

We have been using FASTCGI for a while now, despite putting in sigterm
handlers to get rid of many error, we still occasionally get the followomg
error

FastCGI: comm with (dynamic) server "/var/www/fcgi-bin/[transactions]"
aborted: (first read) idle timeout (30 secs)
FastCGI: incomplete headers (0 bytes) received from server 
"/var/www/fcgi-bin/[transactions]"

When the Process is marked for Termination. Our sigterm handler does some
checking and if the process is still in process then we set a flag and
return back to place it was preempted by the signal handler. Hence we let
the process finish, write some responses to the client and exit.

The Problem here is that if we do return back, in the case when the
transaction is still in process there is a possibility that the database
call has already handed and when it returns back to that position the
process hangs and keeps waiting for the db call to return. In which case we
have a hanging process.

If this happens much to often we would eventually runout of fastcgi max
process and then non of our transactions would work until we restart apache.

Is their any way around it to fix this problem ??? 


Kamran

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/