Re: PoCo HTTP Client not releasing sockets

Rocco Caputo wrote:

> On Fri, Dec 10, 2004 at 02:04:40PM -0800, Mathieu Longtin wrote:
>  
>
> > I just noticed that POE::Component::Client::HTTP does not
> > release socket after HTTPS requests.
> >
> > Anybody encountered that before? 
> >
> > I'm attaching a simple test. You can see the open sockets
> > accumulate by looking at /proc/xxx/fd as the script runs.
> > Towards the end, there are ten open sockets. This doesn't
> > happen when running non encrypted request (HTTP).
> >
> > I tried to do a TRACE_DESTROY on it, but that showed
> > nothing special.
> >
> > Does anyone have an idea where to look to fix this?
> >    
> If you turn it into a Test::More style test, I'll add it to
> Client::HTTP's tests.  That'll fairly ensure that the problem gets
> fixed before the next release.
>
>  
Well, in my dealings with Net::SSLeay::Handle for PoCo::SSLify, I 
noticed that SSLeay does not release the ssl sockets properly, and when 
I hacked Bingos' ircd to use ssl, I saw memory usage zoom up when I ran 
the multi-client connect script...
Upon further investigation, the latest version of SSLify entirely dumps 
Net::SSLeay::Handle, opting to do the whole shebang itself, and tests 
show that it actually gc's the sockets, maybe that's what Rocco should 
do, either add extra code to PoCo::Client::HTTP::SSL to handle the 
destruction, or switch over to SSLify :)
--
Apocalypse

Homepage:       http://JiNxEdStAr.0ne.us
IRC:            Apocalypse@xxxxxxxxxxxx
IRC:            Apocalypse-bot@xxxxxxxxxxxxxxxx
Perl Stuff:     http://search.cpan.org/~APOCAL/