in reply to Re: POE::Component::Client::HTTP, Keepalive, FIN_WAIT_2
in thread POE::Component::Client::HTTP, Keepalive, FIN_WAIT_2

it seems it helped but now I have another behaviour :)

Script works well some time. Then I start to get "connect error 60: Operation timed out", see a lot of "TIME_WAIT" connections in netstat (and no other connections at all) in this moment. after few minutes all TIME_WAIT connections dissapear and I see empty output of netstat, but script still log "Operation timed out".

I've turned on DEBUG in Client::Keepalive and got a lot of following messages at the time when netstat output is empty:

ALLOCATE: enqueuing request for http:gdata.youtube.com:80 at /home/ser +vice/perl/lib/site_perl/5.8.8/POE/Component/Client/Keepalive.pm line +377. ... CON: request from session 5 for address 74.125.95.102 timed out at /ho +me/service/perl/lib/site_perl/5.8.8/POE/Component/Client/Keepalive.pm + line 507.

Replies are listed 'Best First'.
Re^3: POE::Component::Client::HTTP, Keepalive, FIN_WAIT_2
by rcaputo (Chaplain) on Nov 25, 2008 at 17:10 UTC

    I'm not sure I can debug this one from a distance. Can you provide a minimal test case to reproduce the problem? Ideally it would be something I can run without installing proprietary code or data.

    By the way, I released new versions of POE::Component::Client::Keepalive and POE::Component::Client::HTTP with a modified version of the SO_LINGER code and some other bug fixes.