Filing this bug to document an issue I'm working on, reported by ConnectingGTA. The new MLLP implementation seems to behave in the following incorrect way:
When an MLLP start character is received, then part of a message comes across, then the socket times out, the partial message is returned as a complete message by the MLLP implementation, even though no MLLP end block has been received.
An exception is then thrown when the final set of data comes across. This does not seem to match the old implementation, which was quite forgiving in the case of long delays between data blocks.
This should be easy to fix, committing a test case today.
Fix checked in.
Note that this issue affected only HAPI 2.2-beta1 as it is related to the new MLLP implementation.