Menu
▾
▴
Re: [naviserver-devel] Ns_ConnSend
|
From: Stephen D. <sd...@gm...> - 2006-02-27 08:36:57
|
Give it a shot now.
On 2/26/06, Vlad Seryakov <vl...@cr...> wrote:
> ns_register_proc GET /ns_return_big {ns_return 200 text/plain [string
> repeat " " 32768] }
>
> Then try several times to hit your server /ns_return_big
> ns_info threads will show running threads which never exit:
>
> {-conn:ossweb:0 -driver- -1338524752 0 1140991547 ns:connthread {1
> 192.168.0.9 running GET /ns_return_big 16.526732 114674}}
>
> Stephen Deasey wrote:
> > How can I reproduce this problem? If you could write a short test, I
> > can take a look at this.
> >
> >
> > On 2/26/06, Vlad Seryakov <vl...@cr...> wrote:
> >> I am still debugging this i as i see the probkem is in the Ns_ConnSend
> >> now, SockSend is called with nbufs 0 but there are still data to be se=
nt.
> >>
> >> #3 0xb11f54f0 in ?? ()
> >> (gdb)
> >> #4 0xb7d1a728 in sendmsg () from /lib/tls/libc.so.6
> >> (gdb)
> >> #5 0xb7ec8331 in SockSend (sock=3D0, bufs=3D<value optimized out>,
> >> nbufs=3D-1323346704) at sock.c:912
> >> 912 n =3D sendmsg(sock, &msg, 0);
> >> (gdb)
> >> #6 0xb7ec83bc in Ns_SockSendBufs (sock=3D6, bufs=3D0xb11f55dc, nbufs=
=3D0,
> >> timeoutPtr=3D0xb11f5578)
> >> at sock.c:115
> >> 115 n =3D SockSend(sock, bufs, nbufs);
> >> (gdb)
> >> #7 0xb72d5452 in SockProc (cmd=3DDriverSend, sock=3D0xb7ef1580,
> >> bufs=3D0xb11f55dc, nbufs=3D-1323346704)
> >> at nssock.c:120
> >> 120 n =3D Ns_SockSendBufs(sock->sock, bufs, nbufs, &timeou=
t);
> >> (gdb)
> >> #8 0xb7eb1477 in NsSockSend (sockPtr=3D0xb7ef1580, bufs=3D0x0, nbufs=
=3D0) at
> >> driver.c:761
> >> 761 return (*sockPtr->drvPtr->proc)(DriverSend, sock, bufs, nb=
ufs);
> >> (gdb)
> >> #9 0xb7eadf22 in Ns_ConnSend (conn=3D0x80a40f8, bufs=3D0xb11f965c, nb=
ufs=3D1)
> >> at connio.c:219
> >> 219 sent =3D NsSockSend(connPtr->sockPtr, sbufs, sn);
> >> (gdb) p sn
> >> $1 =3D 0
> >> (gdb) p n
> >> $3 =3D 1
> >> (gdb) p towrite
> >> $4 =3D 3204
> >> (gdb) p nwrote
> >> $6 =3D 49152
|
