[Seaside]
Seaside Ports getting tied up (was WAKom not responding to requests)
Derek Brans
brans at nerdonawire.com
Mon Apr 7 09:44:02 CEST 2003
I like the pun in the subject. :)
I felt my original post was being lost in the previous thread, so here it is again. WAKom sometimes stops receiving requests, even when other commanche services do. This continues until I start WAKom on another port.
These are the result of running netstat at different times while the same image is running, without any response from WAKom. Does anyone make anything out of this?
Thank you,
Derek
First, just after I reboot my image:.
netstat -an | grep 8002
tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
then when I try to access seaside
netstat -an | grep 8002
tcp 500 0 127.0.0.1:8002 127.0.0.1:2015 ESTABLISHED
tcp 0 0 127.0.0.1:2015 127.0.0.1:8002 ESTABLISHED
tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
then again later when I try to access seaside again.
netstat -an | grep 8002
tcp 500 0 127.0.0.1:8002 127.0.0.1:2017 ESTABLISHED
tcp 0 0 127.0.0.1:2017 127.0.0.1:8002 ESTABLISHED
tcp 501 0 127.0.0.1:8002 127.0.0.1:2015 CLOSE_WAIT
tcp 0 0 127.0.0.1:2015 127.0.0.1:8002 FIN_WAIT2
tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
Derek Brans
Nerd on a Wire
Web design that's anything but square
http://www.nerdonawire.com
phone: 604.874.6463
mailto: brans at nerdonawire.com
------------------------------------------------------------------------------
_______________________________________________
Seaside mailing list
Seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lnx-12.ams-2.theinternetone.net/pipermail/seaside/attachments/20030407/77c37b33/attachment.htm
More information about the Seaside
mailing list