Do I need to close expired connections in Apache HttpAsyncClient as is done with HttpClient?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Do I need to close expired connections in Apache HttpAsyncClient as is done with HttpClient?
I just double-checked the source code. Yes, one still has to explicitly evict expired connections from the pool. However, the underlying NIO channel and socket will get closed and released immediately. The problem with expired connections not being automatically evicted from the pool is a bug in HttpAsyncClient 4.0 beta3. Feel free to raise a JIRA for this defect.