Double actions in OH2

I don’t know exactly why and how and what, but I have the feeling, that some actions are executed double times. I don’t see a pattern or rule, but only some indications in logs and in the persistance on this behaviour.

e.g. after saving mysql.persist, binder.items, binder.things, binder.rules and binder.sitemap this is in openhab.log:

2016-12-10 12:04:23.736 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'mysql.persist'
2016-12-10 12:04:23.904 [ERROR] [sql.internal.MysqlPersistenceService] - mySQL: Unable to find table for query 'gRTR'.
2016-12-10 12:04:24.682 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'mysql.persist'
2016-12-10 12:04:24.770 [ERROR] [sql.internal.MysqlPersistenceService] - mySQL: Unable to find table for query 'gRTR'.
2016-12-10 12:10:35.458 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.items'
2016-12-10 12:10:35.642 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.items'
2016-12-10 12:10:36.438 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.things'
2016-12-10 12:10:36.530 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.things'
2016-12-10 12:10:37.872 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.rules'
2016-12-10 12:10:38.122 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.rules'
2016-12-10 12:10:39.473 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.sitemap'
2016-12-10 12:10:39.580 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'binder.sitemap'

And also the persistance is fired doubled, I guess, at least this strategy * : strategy = everyDay, restoreOnStartup fires double, as I get every item persisted at 2016-12-10 00:00:01 and 2016-12-10 00:00:02.

Perhaps this is why sometimes the Nuki Smartlock gets confused, if it gets the same API-call double and wifey complains, the door doesn’t open. :frowning:

Is this some kind of misconfiguration on my side? or a known bug? anyone got the same things?