I ran into the same problem (need one cluster
timer and per node
timer) and ran into this question. So, for everyone who is interested in:
If you declare a timer using @Schedule (..., persistent = true), you will get a cluster
timer stored in db timer (which can be migrated)
If you declare a timer with @Schedule (..., persistent = false), you will get a node
timer that will not be saved in the db timer (which cannot be carried over)
source share