org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.QRTZ_EXCL_LOCKS' directly or indirectly in database 'dotcms' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. [See nested exception: java.sql.SQLException: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.QRTZ_EXCL_LOCKS' directly or indirectly in database 'dotcms' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.]


Solutions on the web

Solution icon of github
. You cannot use snapshot isolation to access table 'dbo.QRTZ_EXCL_LOCKS' directly or indirectly in database 'dotcms' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.]

Stack trace

org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.QRTZ_EXCL_LOCKS' directly or indirectly in database 'dotcms' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. [See nested exception: java.sql.SQLException: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.QRTZ_EXCL_LOCKS' directly or indirectly in database 'dotcms' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.]
	at org.quartz.impl.jdbcjobstore.UpdateLockRowSemaphore.executeSQL(UpdateLockRowSemaphore.java:107)
	at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:112)
	at org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:235)
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.removeTrigger(JobStoreSupport.java:1458)
	at org.quartz.core.QuartzScheduler.unscheduleJob(QuartzScheduler.java:965)
	at org.quartz.core.QuartzScheduler.deleteJob(QuartzScheduler.java:932)
	at org.quartz.impl.StdScheduler.deleteJob(StdScheduler.java:278)
	at com.dotmarketing.quartz.QuartzUtils.removeJob(QuartzUtils.java:543)
	at com.dotmarketing.quartz.QuartzUtils.removeJob(QuartzUtils.java:506)
	at com.dotcms.enterprise.publishing.sitesearch.ESSiteSearchAPI.deleteTask(SourceFile:389)
	at com.dotmarketing.sitesearch.ajax.SiteSearchAjaxActionTest.scheduleJob(SiteSearchAjaxActionTest.java:71)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.