Someone from Geronimo mentioned that this problem was actually fixed in the Geronimo version a while back. Perhaps something we should look into or inquire about.
Jeff can you give us an update on that? Alex On Jan 28, 2008 12:25 PM, Julien Vermillard <[EMAIL PROTECTED]> wrote: > Hi, > Following an IRC convo, between alex, tazle and me : > > We had a few complaint recently about remaining unclosed socket and > thread after multiple connection using the NioSocketConnector or simply > the AsyncHttpClient not releasing correctly file descriptor on linux. > > The problem for AsyncHttpClient is was because each connection create a > NioSocketConnector and forget to .dispose() it. > > When you connect and close a session a thread will remain in the > threadpool for 1 minute (it's the default behaviour), you can still > overide it specifying another Executorfilter behaviour. > > BTW AHC is using 1 SocketConnector per AHC instance, I think it should > be changed to share it. > > Julien >
