Affects Version/s: 7.0.0 DXP FP44, 7.0.X, Master
Fix Version/s: None
Component/s: Portal Services > Scheduler
1) create a module with a MessageListener that is registered through the schedulerHelperEngine
2) add a persistent job that is going to fire for that message listener
3) shut down the portal and wait for the trigger time to pass
4) start up the portal
5) if your module loads after quartz, the messageListener will not be registered in time to pick up the job that is triggered, and the job will be missed.
The deployment order matters. In order for the messageListener to receive the job, it must be ready when the message is sent.
We need to find a way to delay the quartz job start until the messageListener becomes available in the OSGI container