You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/05/23 08:48:00 UTC
[jira] [Created] (UNOMI-572) Design issue with SchedulerService and conf reloading.
Kevan Jahanshahi created UNOMI-572:
--------------------------------------
Summary: Design issue with SchedulerService and conf reloading.
Key: UNOMI-572
URL: https://issues.apache.org/jira/browse/UNOMI-572
Project: Apache Unomi
Issue Type: Bug
Affects Versions: 1.6.0, 2.0.0
Reporter: Kevan Jahanshahi
The SchedulerService implementation is part of the *unomi-services* bundle, so in case somebody is editing a configuration file like this one:
{code:java}
org.apache.unomi.services {code}
The SchedulerService will be restarted, and some tasks/timers will be lost during the process, because not all tasks/timers are coming from the *unomi-services* bundle.
There is other bundles that would need to be notify about that restart to be able to re-register their tasks and timers.
Currently those tasks/timers coming from other bundles are lost, and this is causing major Unomi runtime instabilities.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)