EJB timers behavior in a cluster when the database persistence is used in EAP 7
Issue
- If running in a cluster and some of EJB timers need run on only one host and some need to run on all host how can I achieve that?
- If we follow the documentation and enable database persistence the job just run on one of the host in the cluster and we cannot make it run all hosts. What could be the solution?
- Is it possible to run timers marked with @Schedule on all cluster instances even if a shared database is used?
- How ejb timers behave if the persistence use a shared database?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
