KB Article #180845
UNA/B segment not found thrown in TE logs
Problem
-- getting this error in the trading engine logs :
ERROR [Worker22-4225] (EdifactParser.getAsciiInputStream:170) - UNA/B segment not found
-- there is no impact on the processing of the messages
-- how to identify the message causing the problem ?
-- what are the possible causes of this error ?
Resolution
* it can be at least 2 reasons why this error occurs :
- a map produces an EDIFACT message in output, but the message is not enveloped (no Outbound agreement configured for the related flow). Interchange do not expect an EDIFACT message with no UNA, and throws the error
- in the output tab of the service, the format is set as EDIFACT, but the output is not EDIFACT (can be XML, InHouse...). Interchange expects an EDIFACT message, but receives another format and then throw the error
* there is no details in the error message to identify the message that causes the error. It is possible to set the debut to retrieve the coreid (and then the logger ID from the Message Tracker), to find out what is the message :
In <B2Bi installation>Interchange/conf/log4j2.xml file, <Loggers> section, add a line:
<Logger name="com.cyclonecommerce.collaboration.rules.actions.ParseEdiAction" level="DEBUG" />
A restart of Interchange is not necessary.
At next occurence, you will get the details :
2020-01-28 15:15:29,732 - DEBUG [Worker4-56501] (ParseEdiAction) - Failed to parse the message as EDI. This can be OK if the configuration attempts multiple parsers.ci1580220929547.10793363@denu03ms0170_te
com.cyclonecommerce.collaboration.parsers.UnableToParseException: UNA/B segment not found
...
...
* in versions higher than 2.6, the error will be changed to a warning, as it does not affect the processing of the message