W3C home > Mailing lists > Public > www-lib@w3.org > July to September 1999

RE: libww pipelining bug?

From: Olga Antropova <olga@goliath.eai.com>
Date: Wed, 29 Sep 1999 18:07:37 -0500 (CDT)
Message-ID: <XFMail.990929180737.olga@eai.com>
To: Mikhail Grouchinski <mgrouch@usa.net>
Cc: www-lib@w3.org
Hi Mikhail,

Is that the requests are not failing but hanging unhandled in pipeline?
Trace may help. I used the plocking sockets and in some cases if one request
fails then all the subsequent requests to the same host would fail. I
(partially) fixed the problem returning HT_CLOSED instead of HT_ERROR from
HTWriter_write on broken pipe error. Also if you can stop in debugger in
HTWriter_write at the line where broken pipe is handled and look at the stack
- you can see that several functions do not check the return value of
HTWriter_write and just continue (to write on closed socket). That happens in
HTTPReq.c an d HTTPGen.c. In most cases the HT_CLOSED return will be eventually
checked in consecutive writes (and HTHost_recoverPipe be called later) but not
in all.

All that maybe does not have anything in common with your problem, but who
knows :-) ...


On 29-Sep-99 Mikhail Grouchinski wrote:
> When I send GET/POST request with parameters (name1=value1&name2=value2...)
> I recieve a correct reply, but all subsequent requests to the same host 
> stucks in libwww and never return in corresponding callbacks. This doesn't
> happen if I use GET request with no parameters. I use libwww event loop,
> nonblocking sockets, HTTP1.1 with pipelining. Is it a pipelining bug?
> Can anyone give some ideas?
> Thanks,
> Mikhail Grouchinski
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
Received on Wednesday, 29 September 1999 19:08:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:52 UTC