Further responsibilities such as communication with the opposite endpoint is delegated to the next executor in the request execution chain.
If this handler is active, pay particular attention to the placement
of other handlers within the handler chain relative to the retry handler.
Use ChainElement#RETRY as name when referring to this handler.
If a custom handler is placed before the retry handler, the handler will see the initial request and the final outcome after the last retry. Elapsed time will account for any delays imposed by the retry handler.
A custom handler which is placed after the retry handler will be invoked for each individual retry. Elapsed time will measure each individual http request, without the delay imposed by the retry handler.
| Modifier and Type | Field and Description |
|---|---|
| private static final Logger | |
| private final HttpRequestRetryStrategy |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public ClassicHttpResponse | execute(final ClassicHttpRequest
the actual request. request, final ExecChain.the execution scope . scope,the next element in the request execution chain. chain)Implements org. |
| LOG | back to summary |
|---|---|
| private static final Logger LOG | |
| retryStrategy | back to summary |
|---|---|
| private final HttpRequestRetryStrategy retryStrategy | |
| HttpRequestRetryExec | back to summary |
|---|---|
| public HttpRequestRetryExec(final HttpRequestRetryStrategy retryStrategy) | |
| execute | back to summary |
|---|---|
| public ClassicHttpResponse execute(final ClassicHttpRequest request, final ExecChain. Implements org. Doc from org. Executes the actual HTTP request. The handler can choose to return a response message or delegate request execution to the next element in the execution chain.
| |