[HTTPCLIENT-2039] Do not close ConnectionManager in case of Errors

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 4.5.10
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: Thomas Sartissohn
• Created: 18/Dec/19 12:26
• Updated: 06/Aug/20 10:40
• Resolved: 19/Dec/19 13:11

Description

The MainClientExec closes the connectionManager in the execute method whenever a java error is received. In my case an OutOfMemoryError was thrown. This ended in a client instance no longer usable cause the pool was already shut down. And therefore the real error (OutOfMemoryError) was covered by many "Connection pool shut down" exceptions.

I agree that the OutOfMemoryError  is a severe issue which should be covered somehow. But closing the pool is unexpected here.

Is there a chance to remove the closing part and keep the pool running in error case?