[ https://issues.jboss.org/browse/WFLY-11590?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-11590: ------------------------------- Steps to Reproduce: 1.) 2 WildFly server with the same configuration using an EJB timer with DB persistence. 2.) the attached application ({{playground-jar.jar}}) that starts 2 timer (1 _scanner_ timer and 1 _future_ timer) - the _scanner_ timer runs every couple of seconds (e. g. 4 sec) - the _future_ timer will never execute, it is always only _cancelled_ and newly _created_ by the _scanner_ timer (always adding 1 hour) 3.) running both servers with simple {{standalone.xml}} with persistent database timer with a _refresh-interval_ of 2000 (2 seconds) configuration and a port offset It can be observed that the output for {{getTimers()}} on one node will increase in it's number. was: 1.) 2 WildFly server with the same configuration using an EJB timer with DB persistence. 2.) the attached application that starts 2 timer (1 _scanner_ timer and 1 _future_ timer) - the _scanner_ timer runs every couple of seconds (e. g. 4 sec) - the _future_ timer will never execute, it is always only _cancelled_ and newly _created_ by the _scanner_ timer (always adding 1 hour) 3.) running both servers with simple {{standalone.xml}} with persistent database timer with a _refresh-interval_ of 2000 (2 seconds) configuration and a port offset It can be observed that the output for {{getTimers()}} on one node will increase in it's number. -- This message was sent by Atlassian Jira (v7.12.1#712002)