Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

Deadlock found when trying to get lock; try restarting transaction #4024

nini10 ·

My server got stuck so it was reset, after running again, on one configuration following error message shown:

2018-12-26 00:28:56 - could not execute statement
caused by: Deadlock found when trying to get lock; try restarting transaction
Query is: /* update com.pmease.quickbuild.model.Configuration / update QB_CONFIGURATION set QB_ERROR_MESSAGE=?, QB_STATUS_DATE=? where >QB_ID=?, parameters [ ,'2018-12-25 22:28:56.427',11]
caused by: Deadlock found when trying to get lock; try restarting transaction
Query is: /
update com.pmease.quickbuild.model.Configuration */ update QB_CONFIGURATION set QB_ERROR_MESSAGE=?, QB_STATUS_DATE=? where >QB_ID=?, parameters [ ,'2018-12-25 22:28:56.427',11]

In server log found this:

018-12-26 00:28:56,451 [pool-1-thread-1] WARN  org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 1213, SQLState: 40001
2018-12-26 00:28:56,456 [pool-1-thread-1] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Deadlock found when trying to get lock; try restarting transaction
    Query is: /* update com.pmease.quickbuild.model.Configuration */ update QB_CONFIGURATION set QB_ERROR_MESSAGE=?, QB_STATUS_DATE=? where QB_ID=?, parameters [<null>,'2018-12-25 22:28:56.427',11]

Any idea how to solve it?

  • replies 1
  • views 23
  • stars 0
robinshen ADMIN ·

This normally happens when system is doing database backup which takes too long to complete. Please schedule your builds to a different time frame as your database backup to see if it solves the problem.