com.mirth.connect.donkey.server.channel.ChannelException: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Mirth Project | Nick Rupley | 3 years ago
  1. 0

    I had a JavaScript Reader channel (pruning enabled) that was basically just blasting a bunch of messages. At the same time, I ran the data pruner. When I did that, both the pruner and channel processing seemed to stop for a good 15-20 seconds, after which I got this: {code}[2013-06-27 18:48:45,546] ERROR (com.mirth.connect.donkey.server.channel.Channel:961): Error processing message. com.mirth.connect.donkey.server.channel.ChannelException: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:920) at com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:130) at com.mirth.connect.connectors.js.JavaScriptReceiver.poll(JavaScriptReceiver.java:100) at com.mirth.connect.donkey.server.channel.PollConnector$PollConnectorTask.run(PollConnector.java:111) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)Caused by: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertContent(JdbcDao.java:233) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertMessageContent(JdbcDao.java:161) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:98) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:74) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:61) at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:907) ... 5 moreCaused by: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2894) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2334) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:643) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:707) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertContent(JdbcDao.java:230) ... 10 more{code}

    Mirth Project | 3 years ago | Nick Rupley
    com.mirth.connect.donkey.server.channel.ChannelException: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  2. 0

    I had a JavaScript Reader channel (pruning enabled) that was basically just blasting a bunch of messages. At the same time, I ran the data pruner. When I did that, both the pruner and channel processing seemed to stop for a good 15-20 seconds, after which I got this: {code}[2013-06-27 18:48:45,546] ERROR (com.mirth.connect.donkey.server.channel.Channel:961): Error processing message. com.mirth.connect.donkey.server.channel.ChannelException: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:920) at com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:130) at com.mirth.connect.connectors.js.JavaScriptReceiver.poll(JavaScriptReceiver.java:100) at com.mirth.connect.donkey.server.channel.PollConnector$PollConnectorTask.run(PollConnector.java:111) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)Caused by: com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertContent(JdbcDao.java:233) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertMessageContent(JdbcDao.java:161) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:98) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:74) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:61) at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:907) ... 5 moreCaused by: java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2894) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2334) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:643) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:707) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertContent(JdbcDao.java:230) ... 10 more{code}

    Mirth Project | 3 years ago | Nick Rupley
    java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  3. 0

    Forum thread: http://www.mirthcorp.com/community/forums/showthread.php?t=9537 \\ \\ {quote}We have numerous inbound channels that are MLLP listeners sending to multiple channel-reader type destinations. Everything is queued and none of it is synchronized. Frequently, this configuration produces a deadlock while updating the message statistics for the channel and destinations: \\ \\ {code} [2013-11-03 18:47:36,366] ERROR (com.mirth.connect.connectors.vm.VmDispatcher:510): Error processing queued message 215-3 (SENT) for channel 8c89cb69-b26d-450e-a9fc-d09207d9b6eb (Destination 3). This error is expected if the message was manually removed from the queue. com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.addChannelStatistics(JdbcDao.java:369) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.commit(JdbcDao.java:1581) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:131) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:74) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:61) at com.mirth.connect.donkey.server.channel.DestinationConnector.run(DestinationConnector.java:498) at java.lang.Thread.run(Unknown Source)Caused by: java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2894) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2334) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:643) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:707) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.addChannelStatistics(JdbcDao.java:346) ... 6 more{code} Turning the synchronization (wait for previous channel...) on makes this issue go away, but makes our processing sequential -- which we would like to avoid. I've attached the offending configuration, and I can get it to reliably trigger using a set of about 500 messages pumped at it. I've started to look at the way the code for the channels queues up the events for processing based on the Deadlock Graph included in the ZIP file -- but that is as far as I have gotten thus far. Just wanted to see if anyone else had seen this and if anybody was out ahead of me on the analysis. Oh -- the messages do get delivered, it is just the stat updates that are failing. +*Environment:*+ * Windows Server 2008 R2 * Mirth Connect Server 3.0.0.6931 * Built on September 30, 2013 * Server ID: 2f1516e3-8ed6-443e-914f-c670e8fde5cf * Java version: 1.7.0_45 (64-bit) * SQL Server 2008 R2 & SQL Server 2012 Cordially, Jonathan Lent {quote}

    Mirth Project | 3 years ago | Nick Rupley
    java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Forum thread: http://www.mirthcorp.com/community/forums/showthread.php?t=9537 \\ \\ {quote}We have numerous inbound channels that are MLLP listeners sending to multiple channel-reader type destinations. Everything is queued and none of it is synchronized. Frequently, this configuration produces a deadlock while updating the message statistics for the channel and destinations: \\ \\ {code} [2013-11-03 18:47:36,366] ERROR (com.mirth.connect.connectors.vm.VmDispatcher:510): Error processing queued message 215-3 (SENT) for channel 8c89cb69-b26d-450e-a9fc-d09207d9b6eb (Destination 3). This error is expected if the message was manually removed from the queue. com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.addChannelStatistics(JdbcDao.java:369) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.commit(JdbcDao.java:1581) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:131) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:74) at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:61) at com.mirth.connect.donkey.server.channel.DestinationConnector.run(DestinationConnector.java:498) at java.lang.Thread.run(Unknown Source)Caused by: java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2894) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2334) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:643) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:707) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.addChannelStatistics(JdbcDao.java:346) ... 6 more{code} Turning the synchronization (wait for previous channel...) on makes this issue go away, but makes our processing sequential -- which we would like to avoid. I've attached the offending configuration, and I can get it to reliably trigger using a set of about 500 messages pumped at it. I've started to look at the way the code for the channels queues up the events for processing based on the Deadlock Graph included in the ZIP file -- but that is as far as I have gotten thus far. Just wanted to see if anyone else had seen this and if anybody was out ahead of me on the analysis. Oh -- the messages do get delivered, it is just the stat updates that are failing. +*Environment:*+ * Windows Server 2008 R2 * Mirth Connect Server 3.0.0.6931 * Built on September 30, 2013 * Server ID: 2f1516e3-8ed6-443e-914f-c670e8fde5cf * Java version: 1.7.0_45 (64-bit) * SQL Server 2008 R2 & SQL Server 2012 Cordially, Jonathan Lent {quote}

    Mirth Project | 3 years ago | Nick Rupley
    com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  6. 0

    Spring WebFlow: persistence-context not working with Spring Data JPA / Hibernate

    Stack Overflow | 3 years ago | Miguel Angel Merino Vega
    java.sql.SQLException: No se puede actualizar la columna de identidad 'Id'.

  1. vmuller 2 times, last 10 months ago
5 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.sql.SQLException

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

    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic()
  2. jTDS
    JtdsPreparedStatement.executeUpdate
    1. net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
    2. net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2894)
    3. net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2334)
    4. net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:643)
    5. net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:614)
    6. net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:573)
    7. net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:707)
    7 frames
  3. com.mirth.connect
    PollConnector$PollConnectorTask.run
    1. com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertContent(JdbcDao.java:230)
    2. com.mirth.connect.donkey.server.data.jdbc.JdbcDao.insertMessageContent(JdbcDao.java:161)
    3. com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:98)
    4. com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:74)
    5. com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:61)
    6. com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:907)
    7. com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:130)
    8. com.mirth.connect.connectors.js.JavaScriptReceiver.poll(JavaScriptReceiver.java:100)
    9. com.mirth.connect.donkey.server.channel.PollConnector$PollConnectorTask.run(PollConnector.java:111)
    9 frames
  4. Java RT
    TimerThread.run
    1. java.util.TimerThread.mainLoop(Unknown Source)
    2. java.util.TimerThread.run(Unknown Source)
    2 frames