-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow retries to be enabled on default Apache HTTP client #2408
Comments
@ksola PRs can go against the the use of by the way - are you aware of but if you feel this custom |
@ptrthomas Thanks for the fast replay. We have setup a timeout of 1 minute and anyway we get this exception. Yes I know the
I will create a PR to make this retry optional as you suggested. My only concern is the naming of the filed. As we will retry on a concert exception then maybe the name should be |
@ksola you are right, please proceed with |
@ptrthomas I created the PR: #2409 |
1.4.1 released |
In our company we are using Karate test to monitor our production environment every 30 minutes. We encounter at least 5-10 times every week a failing test because of this exception:
org.apache.http.NoHttpResponseException: The target server failed to respond, http call failed after 5010 milliseconds for url:..
After reruning that test this exception does not occur anymore. It was not possible to reproduce that exception because this happen in random tests in our 30 minutes monitors from time to time. That's why it is hard to provide code which will reproduce the problem.
Luckily I found that this is a problem related with
org.apache.httpcomponents:httpclient
which is not the best in handling steal connections. In stack overflow is a proposed solution: https://stackoverflow.com/a/10680629I applied that solution from above stackoverflow to our monitoring tests and the problem does not occur anymore since 3 months.
The commit can be found here: master...ksola:karate:master
Is this fix worth to put int the master branch of karate?
The text was updated successfully, but these errors were encountered: