eclipse-ee4j / eclipse-ee4j/jersey
NoHttpResponseException with one of the APIs when using ApacheConnectorProvider
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
We use Jersey Client with the `ApacheConnectorProvider` for making some of the API calls. When we make one of the API calls, the `NoHttpResponseException` pops up, but because the `ApacheConnectorProvider` is configured to do 3 retries automatically, it retries, and eventually succeeds. However, if I change the retryHandler to not retry, then the API call fails due to the above exception. We would like to understand, under what conditions, does this exception occur?
When I replaced the `connectionReuseStrategy` of the ApacheConnectorProvider to use `NoConnectionReuseStrategy` and changed the retryHanlder to not retry, I was able to resolve the aforementioned error. However, this caused regression in our API calls since we're not reusing connections. We want to be able to reuse connections and also not hit `NoHttpResponseException`.
Please help us understand why the `NoHttpResponseException` is thrown?
Contributor guide
Assessment
This issue has not been assessed yet.