Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
dparmar77 opened this issue Dec 14, 2023 · 0 comments

Comments

@dparmar77
Copy link

dparmar77 commented Dec 14, 2023

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:
image

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 pacmano1 converted this issue into discussion #6027 Dec 14, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant