Ensemble Accepting Unexpected ASTM Message Format
Hello,
I am receiving the following message structure on Ensemble from a lab machine, and it is still being processed. I am using the ASTM format with the EnsLib.EDI.ASTM.Service.TCPService service. I have reviewed multiple ASTM messages and verified the schema structure. Logs are not showing any error or TCP connection is not disconnecting. I am not able to understand why am I receiving this. Please let me know if any additional details are required.
Comments
The issue of receiving ASTM messages in an unexpected format, while using the EnsLib.EDI.ASTM.Service.TCPService, can depend on how the sending system formats the ASTM messages, specifically in relation to line terminators or control characters. Here are possible considerations and actions:
-
To handle cases where line terminators are inconsistent (for example, only using
<CR>instead of<CR><LF>), you might need to extend the base class and customize the processing logic. For instance, you can override the$C(13)character in methods likeOnProcessInput()to replace or adjust terminators 12. -
If you are receiving consecutive ASTM E1394 messages without the standard
ENQ/EOTcontrol characters and they appear as merged, you can use an extended business service with theEOTOPTIONALparameter. Adding this parameter to allow reception of consecutive messages not separated by control characters may help:Parameter EOTOPTIONAL = 1;After this adjustment, use the custom subclass within your production 34.
If these options don’t resolve the issue, you might need specific customization aligned with the format provided by the lab machine or to examine logs for further detail.
Sources: