Behaviour of EJB Timers if a new version of an application is deployed in EAP6 or EAP7

Solution Verified - Updated -

Issue

  • If a new version of an application is deployed we expect that the persistent timers are continued. But this is not the case, all previous active timers are lost.
  • we have an application with name testapp-1.0.0-1.ear that is using ejb-timers. When we upgrade the application with a new version, we got problem with the persistence under the "data/timer-service-data"-directory. Because we have the version in both ear, and war-files, we got a lot of directorys under JBOSS_HOME/data/timer-service-data.
testapp-ear-1.0.0-1.testapp-war-1.0.0-1.TestApiClient
testapp-ear-1.0.0-2.testapp-war-1.0.0-2.TestApiClient

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.