-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] TCP receiver connector fails with UTF16-BE encoding using double byte MLLP #6048
Comments
I thought MLLP simply does not support multi-byte start and end delimiters, although the message itself can be UTF-16. Are you saying if you send an UTF-16 message with standard single byte delimiters it fails? |
With default MLLP settings, start and end sequence are sent as single byte and it works tested as above (Mirth to Mirth). However the software I'm connecting to uses double Byte MLLP when Unicode option is activated. |
Got a link to that software documentation? Got a wireshark capture of the gateway itself? Curious. |
Captured_ORU_Draeger_Unicode.zip |
What ends up happening is Mirth is seeing the packet as two messages, one an empty message, The |
@cmongolang We were successful in using the UTF-16LE where the nulls are after the start and end characters. Is it possible to use that instead of UTF-16BE with Draeger Infinity Gateway? |
We have found a solution for this problem. I will let you know when we are able to publish it. |
Describe the bug
TCP receiver connector fails to receive UTF16-BE data when the MLLP start / end sequence is double byte.
To Reproduce
Expected behavior
The message should be interpreted as UTF16-BE
Actual behavior
A blank message is received, and an error is recorded "Unable to parse, message is null or too short: "
Screenshots
capture_UTF16-BE-_default_MLLP.zip
UTF16 Test-channel_Group.zip
Environment (please complete the following information):
Additional context
Double byte MLLP is required for Draeger Infinity Gateway unicode (UTF-16) HL7 interfaces
It also fails using TCP transmission mode.
The text was updated successfully, but these errors were encountered: