In the process of setting Camel message headers from the payload, the MllpTcpServerConsumer is logging an error when it fails to identify the MSH segment of the message. This error is logged before the hl7Headers configuration option is checked, so the error is always logged - even if setting the HL7 headers is disabled (i.e. hl7Headers=false).
This is a minor issue, but it effects edge cases where non-HL7 payloads are sent with the MLLP protocol.
The logic should be changed such that if the hl7Headers option is false, don't do anything (i.e. no log statement).