Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Http Client Connection Pool Error #1160
The multiple tasks are using the same JerseyClient instance from JerseyClientConfiguration.
After a while, I start getting javax.ws.rs.ProcessingException: java.lang.IllegalStateException: Connection pool shut down
The only way to recover is restarting the application.
This only started to occur in Dropwizard 0.8.2.
Thanks for any help!
After further investigation, it seems that InstrumentedHttpClientConnectionManager shuts down the pool for an unknown reason:
After this point, any HttpClient call, returns an exception _java.lang.IllegalStateException: Connection pool shut down_
PoolingHttpClientConnectionManager shuts down on close() and finalize() method.
When does Dropwizard closes the CloseableHttpClient?
This probably not very helpful, but I figured I would list the places I believe close could be called:
I don't think that's relevant.
The problem described in the Jersey issue is applied only for cases, when user provides own connection manager that's shared between clients. We don't provide such ability, because we create a new connection manager every time user creates a new instance through
I think, we should revert connection manager sharing or at least disable it by default.
@arteam We faced the same issue with dropwizard 0.8.2.