Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


To use the sample application, download and extract the file to your local directory.

Use the mvn install Maven command from the directory that contains the extracted .zip files to build the project and install it in your local repository. The command creates the target/liberty directory that contains your Liberty server, retryTimeoutSampleServer, and starts the server in the background.

To stop the running server, run the Maven command mvn liberty:stop-server. To start the retryTimeoutSampleServer, run the Maven command mvn liberty:start-server.

To access the sample application, visit the http://localhost:9080/retryTimeoutSample/transactions URL.

Without any further configuration, the application is ready to run. You will see a long loading sequence because the application is timing out and retrying using the Timeout and Retry policies from the guide. The server's console log records the number of retries and the time (milliseconds) at which each retry occurred. The time between retry requests is equal to the timeout + delay ± jitter.

To view the console log in real time as the application is retrying requests, run the following or other alternative way to view the file:

tail -f <extract-directory>/target/liberty/wlp/usr/servers/retryTimeoutSampleServer/logs/console.log

Refresh the browser page to run the application again.

Edit the Java files to change the parameter values of the @Timeout and @Retry annotations. If the retryTimeoutSampleServer server is running, run the mvn package Maven command from the directory that contains the extracted .zip file to rebuild the application. The changes take effect without restarting the server. Otherwise, stop the retryTimeoutSampleServer server as indicated and run the mvn install Maven command which will restart the server.


The <extract-directory>/src directory contains the file that is shown throughout the guide. The @Timeout and @Retry annotations that are injected into the code are located in the file.

@Timeout Parameters

The @Timeout annotation accepts a long integer that specifies the timeout in milliseconds. If the request takes this amount of time without responding, a TimeoutException is thrown.

In this sample app, the @Timeout annotation is set to 2000 ms. This value indicates that the request will immediately end and throw a TimeoutException if it has not returned after running for 2000 ms.

@Retry Parameters

The @Retry annotation has many parameters to configure its usage.

  • retryOn specifies the exception class that triggers a retry. The default is java.lang.Exception.class.
  • maxRetries specifies the maximum number of retries. The default is 3.
  • maxDuration specifies the maximum amount of time to perform retries. The default value is 180000.
  • durationUnit specifies the unit of time for maxDuration. The default is ChronoUnit.MILLIS.
  • delay specifies the amount of time to wait between each retry. The default value is 0.
  • delayUnit specifies the unit of time for the delay interval. The default is ChronoUnit.MILLIS.
  • jitter specifies a random variation applied to the delay interval. The default value is 200.
  • jitterDelayUnit specifies the unit of time for jitter. The default is ChronoUnit.MILLIS.
  • abortOn specifies an exception class that stops all retry attempts and fails immediately.

In this sample application, the retryOn parameter is set to TimeoutException.class, telling the Retry policy to retry the showTransactions() method when it returns with a TimeoutException, which comes from the @Timeout annotation.

The maxRetries parameter is set to 4, allowing a maximum of 4 retry requests. The maxDuration is set to 10 and durationUnit is set to ChronoUnit.SECONDS which specifies that the total duration of all retry requests should not last more than 10 seconds. The retry attempts will end when either of the two conditions, maxRetries or maxDuration, is met.

The value for delay is set to 200 and delayUnit is set to ChronoUnit.MILLIS indicating a delay time of 200 milliseconds. The delay time is the wait time between the end of each request and the beginning of the next retry request.

The jitter value is set to 100 and jitterDelayUnit is set to ChronoUnit.MILLIS indicating a jitter of 100 milliseconds. The jitter specifies the variance in the delay time. With the delay of 200 ms and jitter of 100 ms, we can expect delays of 200 ± 100 ms, resulting in delays between 100 to 300 ms.

The abortOn parameter is set to FileNotFoundException.class, indicating that the Retry policy will end immediately if the request throws a FileNotFoundException.

The file contains some configuration variables that control the outcome of the transaction history request for our sample application.

  • sleepTime controls how long the request for the transaction history takes. If this value is greater than the value specified in the @Timeout annotation, the request times out and the browser displays an error message. If this value is less than the @Timeout value, the request is successful and the browser displays the transaction history. Initially in the sample app, the value is set to 2100 milliseconds and the @Timeout value is set to 2000. Therefore, the request times out and the browser displays the message "Your recent transactions are unavailable at this time. Please try again later."
  • abortOnCondition is the sample application's way of simulating a FileNotFoundException. If set to true and the @Retry annotation includes abortOn(FileNotFoundException.class), a FileNotFoundException is thrown and the browser instantly displays the message "Your recent transactions were unable to load." When false, the request is made.
You can’t perform that action at this time.