web stats
Change over from Mirth COnnect 2.x to Mirth 3.x - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Thread Tools Display Modes
Old 01-22-2014, 11:59 AM
Chris Heaton Chris Heaton is offline
What's HL7?
Join Date: Mar 2012
Posts: 3
Chris Heaton is on a distinguished road
Exclamation Change over from Mirth COnnect 2.x to Mirth 3.x

Greetings Folks,

I've been trying to move over a HL7 pass thru that worked just fine in Mirth 2.x

Basically our client is unable to have different ports for their HL7 messages, so we are intercepting them and forwarding on the ADT messages to the ADT Import system.

Now the LLP has changed to TCP Sender with a MLLP

This is fine and dandy but now we get the following error from our TCP Listener.

We aren't sure what to make of it.

Any help is much appreciated.

Error Below----------------

ERROR (com.mirth.connect.connectors.tcp.TcpReceiver:653) : Error receiving message (TCP Listener "Source" on channel 67230900-918a-46c3-9716-53ad6ca08a16).
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at com.mirth.connect.model.transmission.framemode.Fra meStreamHandler.read(FrameStreamHandler.java:121)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:554)
at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe ader.call(TcpReceiver.java:458)
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)
Reply With Quote
Old 01-22-2014, 12:08 PM
narupley's Avatar
narupley narupley is online now
Mirth Employee
Join Date: Oct 2010
Posts: 7,123
narupley is on a distinguished road

Please post the channel you're using so that people here can troubleshoot. That "socket closed" error usually indicates that the remote system is closing the socket before the TCP Listener has a chance to read from it.
Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

Nicholas Rupley
Work: 949-237-6069
Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

- How do I foo?
- You just bar.
Reply With Quote

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:19 PM.

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