Error in mirth log

[anna]

While trying to receive a message from a system to the mirth channel that I have setup,on checking the mirth log i see the following error:

FATAL 2007-03-15 11:34:29,289 [26cc11a0-5cab-4662-aa21-086c7fd56bdb_source_connector._tcpEndpoint#-295453155.receiver.7] org.mule.impl.DefaultComponentExceptionStrategy: The Default Component Exception Strategy has been invoked but there is no current event on the context
FATAL 2007-03-15 11:34:29,289 [26cc11a0-5cab-4662-aa21-086c7fd56bdb_source_connector._tcpEndpoint#-295453155.receiver.7] org.mule.impl.DefaultComponentExceptionStrategy: The error is: Message violates the minimal lower layer protocol: no start of message indicator received.
java.io.IOException: Message violates the minimal lower layer protocol: no start of message indicator received.
at org.mule.providers.tcp.protocols.LlpProtocol.read( LlpProtocol.java:105)
at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.run(TcpMessageReceiver.java:268)
at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
at java.lang.Thread.run(Unknown Source)

what is being expected as the 'start of message indicator' ?

[albertosaez]

Re: Error in mirth log

Hi anna.

The MLLP protocol expects a 0x0B byte as the start of messages

[nshaik]

Re: Error in mirth log

Some systems (like GE Centricity Practice Manager 2004/Millbrook MIK), the HL7 host requires both begin and end character sequence to be specified:

Begin Character Sequence: \x0B
End Character Sequence: \x1C\x0D