rcracel opened a new issue, #16197:
URL: https://github.com/apache/grails-core/issues/16197
Howdy!
I have a feeling there is something simple I am missing here, but I have a
set of jobs that I allow users to modify the triggers at runtime on the
application. This really works well, and I can see that the updated cron
expression get stored in the database as well as updated on the job itself.
My challenge is that when my application restarts, Quartz takes the trigger
configuration defined in the job itself and overrides (updates) the value
previously stored in the database. For instance, I have a job where I define a
trigger as follows...
`
static triggers = {
cron cronExpression: '0 15 * ? * * *'
}
`
If I update that expression during runtime, it gets propagated correctly to
the database... let's say I replace the expression with '0 20 * ? * * *' and
check the database for the correct value. All is good until I have to restart
the application.
Once the application restarts I see both the database and the job itself
contain the original '0 15 * ? * * *' expression, whereas I expected the
previously persisted value to win.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
