Re: [jetty-dev] jetty client socket fd leak issue

[Junwei Sun <sun_junwei@xxxxxxxxx>]

Hi Simon,

I understand jetty client has feature to manage connection pool. 
However, in this case, the URL is a bad URL which domain does not exist.
So, there is no connection for this URL at all actually. But the socket fd leaves there, never disappears!
Even I set the idle timeout to be very small, the socket fd is still there.
When I submit more of such URLs' requests, socket fd number increases more and more. At last, the program dies.

So from my point of view, this issue should be a bug in jetty client code.

Thanks.

Regards,
Junwei 
----
I do not think this is a problem.
HttpClient opens and caches connections so even with no requests
outstanding, there will probably be connections opened by previous
requests.
This is done for performances reason.

Idle connections are eventually closed, and the timeout is configurable.

Simon