2026-03-20 14:23:10.422 [WARN ] [el.core.internal.ModelRepositoryImpl] - DSL model 'mysql.persist' has errors, therefore ignoring it: [10,5]: no viable alternative at input 'default'
2026-03-20 14:23:10.430 [WARN ] [el.core.internal.ModelRepositoryImpl] - DSL model 'mapdb.persist' has errors, therefore ignoring it: [2,9]: no viable alternative at input 'default'
Könnt ihr mir helfen woran das liegt?
Bisher hat das immer einwandfrei funktioniert. Nach irgendeinem Update ging das nicht mehr.
/************************************************** MySQL Persistence ********************************************/
// persistence strategies have a name and a definition and are referred to in the "Items" section
Strategies {
// if no strategy is specified for an item entry below, the default list will be used
everyMinute : "0 * * * * ?"
every5Minutes : "0 */5 * * * ?"
everyHour : "0 0 * * * ?"
everyDay : "0 0 0 * * ?"
default = everyChange
}
Items {
// persist all items once a day and on every change and restore them from the db at startup
*: strategy = everyChange, restoreOnStartup
}
Strategies {
default = everyChange
}
Items {
// persist all items once a day and on every change and restore them from the db at startup
*: strategy = everyChange, restoreOnStartup
}
Breaking Changes that Require Manual Interaction after the Upgrade
Changes in Core
Persistence default strategies are removed and not applied automatically anymore. Managed persistence configurations are updated automatically. If you have a file based configuration with an existing .persist file, you may have to update your configuration: remove "default" from Strategies and make sure all Items definitions have a strategy defined.
