web stats
Error routing message to channel with deadlock victim - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 02-12-2015, 09:57 AM
nreddy nreddy is offline
OBX.2 Kenobi
 
Join Date: Jan 2015
Posts: 72
nreddy is on a distinguished road
Default Error routing message to channel with deadlock victim

we are having an channel that just routs the messages to two different channels, in that channel we go this error.
version:3.0.0.6936

Quote:
Channel Writer error
ERROR MESSAGE: Error routing message to channel id: ad80ef9b-bcdf-42c6-9b5b-834302a5fe4c
com.mirth.connect.donkey.server.channel.ChannelExc eption: com.mirth.connect.donkey.server.channel.ChannelExc eption: com.mirth.connect.donkey.server.data.DonkeyDaoExce ption: java.sql.SQLException: Transaction (Process ID 62) 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.di spatchRawMessage(Channel.java:971)
at com.mirth.connect.donkey.server.channel.SourceConn ector.dispatchRawMessage(SourceConnector.java:177)
at com.mirth.connect.server.controllers.DonkeyEngineC ontroller.dispatchRawMessage(DonkeyEngineControlle r.java:496)
at com.mirth.connect.connectors.vm.VmDispatcher.send( VmDispatcher.java:141)
at com.mirth.connect.donkey.server.channel.Destinatio nConnector.handleSend(DestinationConnector.java:54 0)
at com.mirth.connect.donkey.server.channel.Destinatio nConnector.process(DestinationConnector.java:332)
at com.mirth.connect.donkey.server.channel.Destinatio nChain.call(DestinationChain.java:224)
at com.mirth.connect.donkey.server.channel.Channel.pr ocess(Channel.java:1345)
at com.mirth.connect.donkey.server.channel.Channel.pr ocessSourceQueue(Channel.java:1447)
at com.mirth.connect.donkey.server.channel.Channel.ru n(Channel.java:1434)
at java.lang.Thread.run(Unknown Source)
Caused by: com.mirth.connect.donkey.server.channel.ChannelExc eption: com.mirth.connect.donkey.server.data.DonkeyDaoExce ption: java.sql.SQLException: Transaction (Process ID 62) 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.di spatchRawMessage(Channel.java:929)
... 10 more
Caused by: com.mirth.connect.donkey.server.data.DonkeyDaoExce ption: java.sql.SQLException: Transaction (Process ID 62) 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.Buff eredDao.executeTasks(BufferedDao.java:131)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:74)
at com.mirth.connect.donkey.server.data.buffered.Buff eredDao.commit(BufferedDao.java:61)
at com.mirth.connect.donkey.server.channel.Channel.di spatchRawMessage(Channel.java:917)
... 10 more
Caused by: java.sql.SQLException: Transaction (Process ID 62) 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.addDiagnos tic(SQLDiagnostic.java:372)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(Td sCore.java:2894)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCor e.java:2334)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(T dsCore.java:643)
at net.sourceforge.jtds.jdbc.JtdsStatement.processRes ults(JtdsStatement.java:614)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL (JtdsStatement.java:573)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.ex ecuteUpdate(JtdsPreparedStatement.java:707)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao. addChannelStatistics(JdbcDao.java:346)
... 15 more
Reply With Quote
  #2  
Old 02-12-2015, 10:33 AM
cory_cole cory_cole is online now
Mirth Guru
 
Join Date: Mar 2012
Posts: 1,348
cory_cole is on a distinguished road
Default

redeploy the sending channel and ad80ef9b-bcdf-42c6-9b5b-834302a5fe4c. Then reprocess errored messages.
Reply With Quote
  #3  
Old 02-12-2015, 11:06 AM
nreddy nreddy is offline
OBX.2 Kenobi
 
Join Date: Jan 2015
Posts: 72
nreddy is on a distinguished road
Default

just want to know why this error came.
Reply With Quote
  #4  
Old 02-12-2015, 11:11 AM
cory_cole cory_cole is online now
Mirth Guru
 
Join Date: Mar 2012
Posts: 1,348
cory_cole is on a distinguished road
Default

There was a communication error between the two channels. Either the receiving channel wasn't listening as if were deployed. Or the sending channel wasn't seeing it as deployed.
Reply With Quote
  #5  
Old 03-10-2015, 10:21 AM
wayneh wayneh is offline
OBX.3 Kenobi
 
Join Date: May 2012
Posts: 102
wayneh is on a distinguished road
Default

FYI this is why you're seeing the deadlock http://www.mirthcorp.com/community/i...wse/MIRTH-3042

It is a bug that was fixed in 3.0.1.

Note that 3.2.0 is out already so you may want to think about updating.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 11:17 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation