[iolib-devel] stuck sockets
Attila Lendvai
attila.lendvai at gmail.com
Sat Feb 28 15:13:36 UTC 2009
Stelian, i need your help.
our server went non-responsive and my investigation results in this:
all worker threads were waiting here:
15: (IOLIB.STREAMS::%FILL-IBUF IOLIB.SOCKETS::SOCKET-READ-FN 15
#S(IOLIB.STREAMS::IOBUF :DATA #.(SB-SYS:INT-SAP #X00658620) :SIZE 4096
:START 0 :END 0))
16: ((SB-GRAY:STREAM-READ-BYTE
(IOLIB.STREAMS:DUAL-CHANNEL-GRAY-STREAM)) #<active IPv6 stream socket
connected to ::ffff:81.183.137.134/1237 {100F6EEF71}>)
looking at netstat shows that there are exactly as many of these as
stuck threads:
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1249
ESTABLISHED 1004 736341 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1265
ESTABLISHED 1004 736356 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1261
ESTABLISHED 1004 736352 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1237
ESTABLISHED 1004 736329 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1281
ESTABLISHED 1004 736999 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1257
ESTABLISHED 1004 736348 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1273
ESTABLISHED 1004 736363 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1242
ESTABLISHED 1004 736336 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1253
ESTABLISHED 1004 736344 -
tcp6 0 0 192.168.101.105:8080 81.183.137.134:1269
ESTABLISHED 1004 736360 -
do you think that this remote host is really keeping the connection open?
if so, do you think that it will help if i do this on the socket
returned by accept:
(setf (iolib:socket-option stream-socket :receive-timeout) 5)
thanks in advance,
--
attila
More information about the iolib-devel
mailing list