DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • A Systematic Approach for Java Software Upgrades
  • From J2EE to Jakarta EE
  • Exploring Exciting New Features in Java 17 With Examples
  • The Next Evolution of Java: Faster Innovation, Simpler Adoption

Trending

  • TIOBE Index for June 2025: Top 10 Most Popular Programming Languages
  • Converting List to String in Terraform
  • The Shift of DevOps From Automation to Intelligence
  • Taming Billions of Rows: How Metadata and SQL Can Replace Your ETL Pipeline
  1. DZone
  2. Coding
  3. Java
  4. Implementing Auto Retry in Java EE Applications

Implementing Auto Retry in Java EE Applications

How do you handle the problem of inconsistent and unpredictable timeouts? In Java EE a good solution is interceptors.

By 
Abhishek Gupta user avatar
Abhishek Gupta
DZone Core CORE ·
Nov. 06, 15 · Tutorial
Likes (4)
Comment
Save
Tweet
Share
22.2K Views

Join the DZone community and get the full member experience.

Join For Free

Initially, I wanted to call this blog – ‘Flexible timeouts with interceptor driven retry policies‘ – but then I thought it would be too ‘heavy’. This statement, along with the revised title should (hopefully) give you an idea of what this post might talk about ;-)

The Trigger

This post is primarily driven by one of the comment/questions I received on one of my earlier posts which briefly discussed timeout mechanisms and how they can be used to define ‘concurrency policies’ for Stateful and Singleton EJBs.

question

The Problem

While timeouts are a good way to enforce concurrency policies and control resource allocation/usage in your the EJB container, a problem arises when the timeouts are inconsistent and unpredictable. How do you configure your timeout policy then?

Of course, there is no perfect solution. But, one of the work arounds which popped into my mind was, to ‘retry‘ the failed method (this might not be appropriate or possible for your given scenario, but can be applied if the use case permits). This is good example of a ‘cross-cutting‘ concern or in other words, an ‘aspect‘. The Java EE answer for this is – Interceptors. These are much better than the default ‘rinse-repeat-until-xyz with a try-catch block‘ because of

  • code reuse
  • flexibility

The Gist (of the Solution)

Here is the high level description (code available on Github)

  • Define a simple annotation which represents the ‘retry policy metadata’ e.g. number of retries
  • retry-policy

  • Define an interceptor with an implementation to retry the target method – this would use the above mentioned ‘retry policy’ metadata and behave accordingly
  • interceptor

  • Attach this interceptor to the required method (caller)
  • target-class

  • Optionally, use @InterceptorBinding
  • The Sample Code

    • Uses a Singleton EJB to simulate a sample service and introduces latency via the obvious Thread.sleep() [which of course is forbidden inside a Java EE container]
    • Uses a JAX-RS resource which injects and calls the Singleton EJB and is a candidate for ‘retry’ as per a ‘policy’
    • Can be tested by deploying on any Java EE (6 or 7) compatible server and using Apache JMeter to simulate concurrent clients/requests (Invoke HTTP GET on http://serverip:port/FlexiTimeouts/test)

    Without the retry (interceptor) configuration, the tests (for concurrent requests) will result in a HTTP timeout (408).

    without-retry

    Once the retry interceptor is activated, there will be some latency because the task will be automatically retried once it fails. This of course will depend on the volume (of concurrent requests) and the threshold would need to be tuned accordingly – higher threshold for a highly concurrent environment (usually, not ideally)

    Java EE Java (programming language)

    Published at DZone with permission of Abhishek Gupta, DZone MVB. See the original article here.

    Opinions expressed by DZone contributors are their own.

    Related

    • A Systematic Approach for Java Software Upgrades
    • From J2EE to Jakarta EE
    • Exploring Exciting New Features in Java 17 With Examples
    • The Next Evolution of Java: Faster Innovation, Simpler Adoption

    Partner Resources

    ×

    Comments

    The likes didn't load as expected. Please refresh the page and try again.

    ABOUT US

    • About DZone
    • Support and feedback
    • Community research
    • Sitemap

    ADVERTISE

    • Advertise with DZone

    CONTRIBUTE ON DZONE

    • Article Submission Guidelines
    • Become a Contributor
    • Core Program
    • Visit the Writers' Zone

    LEGAL

    • Terms of Service
    • Privacy Policy

    CONTACT US

    • 3343 Perimeter Hill Drive
    • Suite 100
    • Nashville, TN 37211
    • [email protected]

    Let's be friends: