Forum Discussion

jomalladi's avatar
jomalladi
New Contributor
8 years ago

SQL Server - Update deadlock issue

Hello All,
I am getting transaction deadlocked errors while Updating the records. The snap being used here is SQL Server Update.

Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim

Stack Trace :
java.sql.BatchUpdateException: Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeBatch(SQLServerStatement.java:1740) at com.zaxxer.hikari.proxy.StatementProxy.executeBatch(StatementProxy.java:116) at com.zaxxer.hikari.proxy.StatementJavassistProxy.executeBatch(StatementJavassistProxy.java) at org.jooq.tools.jdbc.DefaultStatement.executeBatch(DefaultStatement.java:93) at org.jooq.tools.jdbc.DefaultStatement.executeBatch(DefaultStatement.java:93) at org.jooq.impl.BatchMultiple.execute(BatchMultiple.java:106) at org.jooq.impl.BatchMultiple.execute(BatchMultiple.java:78) at com.snaplogic.snap.api.sql.operations.JdbcOperationsImpl.flushBatch(JdbcOperationsImpl.java:1222) at com.snaplogic.snap.api.sql.operations.JdbcOperationsImpl.update(JdbcOperationsImpl.java:795) at com.snaplogic.snaps.sql.SimpleSqlUpdateSnap.processData(SimpleSqlUpdateSnap.java:130) at com.snaplogic.snaps.sql.SimpleSqlWriteSnap.processDocument(SimpleSqlWriteSnap.java:84) at com.snaplogic.snaps.sql.SimpleSqlSnap.process(SimpleSqlSnap.java:254) at com.snaplogic.snap.api.ExecutionUtil.process(ExecutionUtil.java:88) at com.snaplogic.snap.api.ExecutionUtil.execute(ExecutionUtil.java:100) at com.snaplogic.snap.api.ExecutionUtil.execute(ExecutionUtil.java:68) at com.snaplogic.snap.api.SimpleSnap.execute(SimpleSnap.java:66) at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeSnap(SnapRunnableImpl.java:709) at com.snaplogic.cc.snap.common.SnapRunnableImpl.execute(SnapRunnableImpl.java:489) at com.snaplogic.cc.snap.common.SnapRunnableImpl.doRun(SnapRunnableImpl.java:770) at com.snaplogic.cc.snap.common.SnapRunnableImpl.access$000(SnapRunnableImpl.java:108) at com.snaplogic.cc.snap.common.SnapRunnableImpl$1.run(SnapRunnableImpl.java:335) at com.snaplogic.cc.snap.common.SnapRunnableImpl$1.run(SnapRunnableImpl.java:331) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Unknown Source) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:330) at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:108) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Can you please let me know if you have any ideas on how to deal with this?

Thank you!

2 Replies

  • Dai9210's avatar
    Dai9210
    New Contributor II
    4 years ago

    Get the same issue…Did you find a way to fix this?

    • mbowen's avatar
      mbowen
      Employee
      4 years ago

      Hi @Dai9210

      Deadlock issues can be tricky to debug and often require further research/deeper investigation. Creating a support ticket is recommended, as we’ll try to reproduce the conditions in-house plus get more details about your configuration (versions, etc).

      SQL Server, plus our other db snaps, are actively developed. So, new features have been added and bugs fixed. This snap pack has had many updates in the last 3 years.

      All that said, you could paste a stack trace here if you want, and we may be able to fish out some details. Other details such as SQL Server version, O.S., helpful.