Ok. After fixing the rule which created a lock but never released the lock the stopping cron jobs and rrd4j persistence problems went away. It seams that with a simple forgotten “unlock” you can effectively kill the scheduler…
Now the only remaining problem is the mysql persistence constantly loosing connectivity to the local mysql database. But I will create a new threat for that.