Re: [cgi-devel] Issue with request data and threads
Status: Beta
Brought to you by:
drrngrvy
From: Ankur G. <ank...@gm...> - 2010-08-17 20:11:42
|
Hi Darren, I have encountered another issue. Here is the description: Thread gets a request, processes it but gets an EPIPE while committing the response. The thread could return but instead it continues on to do another accept. At this point, the accept fails with an already open message and the thread exits. How should this case be handled? Thanks, -Ankur On Fri, Aug 13, 2010 at 5:09 PM, Ankur Gupta <ank...@gm...> wrote: > Hi Darren, > > Doing 'new_request->clear()' did fix the issue. > > Thanks, > -Ankur > > > On Thu, Aug 12, 2010 at 2:21 AM, Darren Garvey <lis...@gm...>wrote: > >> Hi Ankur, >> >> On 12 August 2010 08:13, Ankur Gupta <ank...@gm...> wrote: >> >>> >>> I am trying out the code for server3 in cgi/example/fcgi. The server >>> has 10 threads. I am noticing that after sending 10 requests old requests >>> start recirculating EVEN THOUGH the request URL is different. Eg: >>> >> >> <snip description> >> >> What platform are you trying this on? This sounds like the request object >> isn't being reset by the accept() handler. Can you try adding the line: >> >> new_request->clear(); >> >> above the call to accept(*new_request) to see if this helps? >> >> Cheers, >> Darren >> > > |