Hi again, Just to let you know that I have fixed this issue by deleting a stuck record in the "jobStatus" table and restarting Syncope. I dont' know why this record was not cleaned by Syncope itself, I suspect the VM hosting the service (in my dev platform) crashed leaving the database in an inconsistent state. Best regards Lionel
----- Le 13 Oct 26, à 12:04, Lionel SCHWARZ <[email protected]> a écrit : > Hi all, > I'm facing a strange behavior on my 4.0.7 setup for a couple of weeks: > notification tasks are not executed, means mails are not sent. > I have no idea what could change in the configuration since the last time > emails > were sent successfully... > This problem occurs on all notifications. Other tasks (scheduled, reports, > ...) > work fine. > Notification tasks are created properly but never sent: > { "_class": "org.apache.syncope.common.lib.to.NotificationTaskTO", "key": > "01a12e44-7edb-7058-863c-6501f634d6ae", "start": null, "end": null, > "latestExecStatus": "", "lastExecutor": null, "executions": [], > "notification": > "019fa2f3-5cfc-73a1-bb9b-c680f7fbc8c5", "anyTypeKind": "USER", "entityKey": > "019fa343-a09a-771f-ace8-81ee04fb3a4f", ...} > I checked that the trigger param is OK: "notificationjob.cronExpression" is > "0/20 * * * * ?" > The level log set as DEBUG for "org.apache.syncope.core.provisioning" gives > nothing for the DefaultJobManager. > Does anyone has an idea what is wrong here ? > Thanks > Lionel
