1
●0 ●0 ●1
Getting Hex error due to unavailability of feed in Bonds rate. Example you can take bond IN0020170174 . Same issue we faced while doing equity rate testing and you can mentioned case 09130742 as reference for refinitive team.
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
9.6k
●10 ●7 ●7
Hello @treasuryit
According to case 09130742, the application prints the error when it cannot find the required fields in a data message. Based on the info I have, the application expects primact_1 field is in every UPDATE messages but the feed does not publish the field in every UPDATE messages. Hence, the application prints the Hex error for the data messages which do not contain primact_1 field.
I suggest you create a variable which keeps primact_1 data and update the variable according to a data message containing the primact_1 field. Hence, the application can show up-to-date primact_1 data. For a data message which does not contain primact_1 field, you should not print the error because this is not the error but it is data expected behavior that primact_1 field is not necessary to be contained in every data messages. Anyway, you may print the info or the warning that the data message does not contain the field.
Normally, the error should be printed when a data message cannot be unpacked as shown in MDSubDemoClient.java shipped with RFA packages:
catch (TibException te)
{
System.out.println("Unable to unpack data with TibMsg. Displaying hex.");
String rawData = HexDump.hexDump(data, length);
System.out.println(rawData);
}
Hope this help.
