Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
PAYARA-4215: Enable persistent timers in Deployment Group targets #4338
This is a bugfix / feature (bit of both).
Method annotated with
It is task of DAS to register timers defined by annotations and xml descriptor, and in general it couldn't know which timer service defined in domain to use.
However, from now on we will assume, that user is doing the right thing and his instances' timer service configurations are compatible. E. g. point to same external database, or use DataGrid timer service. At this point,
When such application is deployed a warning is printed on DAS:
Persistent timer will now migrate whenever deployment group member disappears (instance shuts down). Therefore, following are limitations to use persistent timers properly and have them correctly migrate:
Used reproducer from payara-4125.zip.
Stopping or killing instances cause persistent timers to migrate to different instance.
Test suites executed
Zulu JDK 1.8_222 on Windows 10 with Maven 3.6.2
Because there is no shared timer service configuration amongst instances in a Deployment Group, it is assumed that user configured the instances properly. Configuration of one of the instances is used to set up annotated timers.
rdebusscher left a comment
Tested this scenario
Deployment is OK, Timer messages in log of 1 instance and warning messages in the log.