com.mirth.connect.model.transmission.framemode.FrameStreamHandlerException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Hello, this is in .7140. After upgrading we noticed an error notification in the console telling us that a channel had thrown an error receiving a message due to a mismatch in the EoM Bytes. The issue I'm reporting as that there was no indication in the channel statistics that this had occurred. It was pure luck that I had spotted the error in the console as this channel doesn't see much traffic. The message also did not appear in the message browser. As a result of this, we were forced to go into Meditech and run audit trails to find what message hadn't gone. Changing the expected EoM bytes eliminated the problem that alerted us to this issue. The error message is pasted below: [2014-05-01 10:13:01,031] ERROR (com.mirth.connect.connectors.tcp.TcpReceiver:657): Error receiving message (TCP Listener "Source" on channel 7be8c64c-2f4c-4d9f-b4d1-06db52ccfbca). com.mirth.connect.model.transmission.framemode.FrameStreamHandlerException: End of message bytes (<FS><CR>) not detected. Last bytes received: <CR><FF> at com.mirth.connect.model.transmission.framemode.FrameStreamHandler.read(FrameStreamHandler.java:221) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:558) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:462) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)
    via by David Rothbauer,
  • Hello, this is in .7140. After upgrading we noticed an error notification in the console telling us that a channel had thrown an error receiving a message due to a mismatch in the EoM Bytes. The issue I'm reporting as that there was no indication in the channel statistics that this had occurred. It was pure luck that I had spotted the error in the console as this channel doesn't see much traffic. The message also did not appear in the message browser. As a result of this, we were forced to go into Meditech and run audit trails to find what message hadn't gone. Changing the expected EoM bytes eliminated the problem that alerted us to this issue. The error message is pasted below: [2014-05-01 10:13:01,031] ERROR (com.mirth.connect.connectors.tcp.TcpReceiver:657): Error receiving message (TCP Listener "Source" on channel 7be8c64c-2f4c-4d9f-b4d1-06db52ccfbca). com.mirth.connect.model.transmission.framemode.FrameStreamHandlerException: End of message bytes (<FS><CR>) not detected. Last bytes received: <CR><FF> at com.mirth.connect.model.transmission.framemode.FrameStreamHandler.read(FrameStreamHandler.java:221) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:558) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:462) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)
    via by David Rothbauer,
    • com.mirth.connect.model.transmission.framemode.FrameStreamHandlerException: End of message bytes (<FS><CR>) not detected. Last bytes received: <CR><FF> at com.mirth.connect.model.transmission.framemode.FrameStreamHandler.read(FrameStreamHandler.java:221) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:558) at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:462) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)
    No Bugmate found.