Triggers deadlocked in the database

Skip to first unread message

Xander Steinmann

Jul 5, 2021, 7:26:14 AM7/5/21
to dotCMS User Group

We have a dotCMS 4.3.2 with MSSQL that has many errors in the logs like this:

[21/06/21 13:57:02:893 CEST] ERROR core.ErrorLogger: An error occured while firing trigger 'group19.trigger19'

org.quartz.JobPersistenceException: Couldn't update states of blocked triggers: The transaction (process ID 79) was on lock resources due to another process in a deadlock situation and was selected as a deadlock victim.Re-execute the transaction. (google translated :))

Is this a dotCMS thing or a MS SQL thing? I'm not sure where to look and I've already tried the standard cache flush / reindex / restart things. We don't have this issue in all dotCMS instances (dev/uat/prod), just in one.

Any help is appreciated.

Kind regards,


Falzone, Chris

Jul 6, 2021, 1:20:31 PM7/6/21
I would start with just taking the environment down and restarting the DB server first. Though if you want to dig in a little further or prevent the down time, look and see if there is a long running transaction in DB.  You could try killing that one instead of a full restart.  If the issue comes back after that, then I am not so sure.  Do you have a lot of custom Quartz Jobs there? Maybe the timing of them needs to be adjusted so that the offending jobs are not running at the same time.  But if it is just one environment, that's probably less likely the case.  I like to follow the 1, 2, ... n principal.  That is: once or twice means it was just a fluke, but the 2nd or 3rd time, then it's time to do a deeper dive into the root cause.  

-- - Open Source Java Content Management
You received this message because you are subscribed to the Google Groups "dotCMS User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit


Christopher Falzone

DevOps Engineer


Xander Steinmann

Jul 7, 2021, 2:33:52 AM7/7/21
to dotCMS User Group
Thanks, Chris. I also think this is a fluke but it's pretty persistent so far :)
We did not do anything with custom code/jobs here so we suspect push publishing may have triggered this. We'll do some more investigating/restarting with the DB.
Kind regards,

Reply all
Reply to author
0 new messages