Mirth TCP LLP channels getting froze sometimes and message stuck in received state

[dparmar77]

I am using Mirth 3.8.1 version and I have around 40 TCP Listener channels . periodically some other channel gets froze and message gets stuck in received status. I am unable to stop/halt the channel. When I try to stop it gets stuck in stopping state. The only way I fix it is I create a clone of it and then restart the Mirth service.

I tried to search for this issue on Mirth forums but can't find a solution to this.
https://forums.mirthproject.io/forum/mirth-connect/support/184334-mirth-tcp-llp-channels-getting-froze-sometimes-and-message-stuck-in-received-state

below is the TCP Listener config I have set:

Checked the Mirth log and below is the error:
ERROR 2023-12-13 19:01:12,780 [Source Queue Thread 2 on TEST Inbound] com.mirth.connect.donkey.server.channel.Channel: An error occurred in channel TEST Inbound while processing message ID 152511 from the source queue
com.mirth.connect.donkey.server.data.DonkeyDaoException: java.sql.SQLException: I/O Error: Connection reset
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.commit(JdbcDao.java:2328)
at com.mirth.connect.donkey.server.data.buffered.BufferedDao.executeTasks(BufferedDao.java:147)
at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:85)
at com.mirth.connect.donkey.server.data.buffered.BufferedDao.commit(BufferedDao.java:72)
at com.mirth.connect.donkey.server.channel.Channel.finishMessage(Channel.java:1936)
at com.mirth.connect.donkey.server.channel.Channel.process(Channel.java:1780)
at com.mirth.connect.donkey.server.channel.Channel.processSourceQueue(Channel.java:1854)
at com.mirth.connect.donkey.server.channel.Channel.run(Channel.java:1840)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: I/O Error: Connection reset
at net.sourceforge.jtds.jdbc.TdsCore.executeSQL(TdsCore.java:1093)
at net.sourceforge.jtds.jdbc.TdsCore.submitSQL(TdsCore.java:938)
at net.sourceforge.jtds.jdbc.JtdsConnection.commit(JtdsConnection.java:2158)
at com.zaxxer.hikari.pool.ProxyConnection.commit(ProxyConnection.java:352)
at com.zaxxer.hikari.pool.HikariProxyConnection.commit(HikariProxyConnection.java)
at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.commit(JdbcDao.java:2325)
... 8 more

Do I need to add ssl=require in mirth db connection string?

[pacmano1]

that looks like you’re having SQL Server connectivity issues. if your connection required, SSL, all your channels would be failing.

[dparmar77]

How do I fix this? It keeps happening occasionally and the channel get freeze and message gets stuck in received status

[pacmano1]

This isn’t a mirth problem per se, you need to troubleshoot SQL server connectivity, that is a complex topic. Would typically involve understanding what is happening on the SQL server at all times with proactive monitoring and possibly network sniffing to understand if traffic is dropping. Sort of out of scope for this forum.

[pacmano1]

I would first switch to the native MSSQL jdbc driver though on the db connect string in mirth.properties (assuming it is there in 3.8.1), you need to upgrade.

Caused by: java.sql.SQLException: I/O Error: Connection reset that is the SQL problem you need to address.