No announcement yet.

Change over from Mirth COnnect 2.x to Mirth 3.x

  • Filter
  • Time
  • Show
Clear All
new posts

  • 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). socket closed
    at Method)
    at Source)
    at Source)
    at Source)
    at Source)
    at com.mirth.connect.model.transmission.framemode.Fra
    at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe
    at com.mirth.connect.connectors.tcp.TcpReceiver$TcpRe
    at Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$ (Unknown Source)
    at Source)

  • #2
    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.