ACK message, nakCode - INVALID_CONTENT, text=Invalid content
We submit events via Refinitiv Real-Time SDK v3.7.1.0 directly to the Refinitiv endpoints (EMA, TunnelStreamRequest, OmmConsumerClient).
In most cases we submit events and get Ok ACK similar to this (according to xml trace output)
<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/11.11.11.11:55888 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Tue Nov 14 09:31:00 EST 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="32" dataSize="65">
<extendedHeader data="0100"/>
<dataBody>
<POST domainType="MARKET_PRICE" streamId="5" containerType="MSG" flags="0x62 (HAS_POST_ID|POST_COMPLETE|ACK)" postId="31" postUserId="0" postUserAddr="0.0.0.0" dataSize="43">
<dataBody>
<UPDATE domainType="MARKET_PRICE" streamId="5" containerType="FIELD_LIST" flags="0x08 (HAS_MSG_KEY)" updateType="0" dataSize="21">
<key flags="0x02 (HAS_NAME)" name=".SOMERIC"/>
<dataBody>
<fieldList flags="0x08 (HAS_STANDARD_DATA)">
<fieldEntry fieldId="6" data="0C17 53"/>
<fieldEntry fieldId="16" data="0E0B 07E7"/>
<fieldEntry fieldId="18" data="0E1F"/>
</fieldList>
</dataBody>
</UPDATE>
</dataBody>
</POST>
</dataBody>
</GENERIC>
<!-- Incoming Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/11.11.11.11:55888 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Tue Nov 14 09:31:00 EST 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="29" dataSize="14">
<extendedHeader data="0100"/>
<dataBody>
<ACK domainType="MARKET_PRICE" streamId="5" containerType="NO_DATA" flags="0x00" ackId="31" dataSize="0">
<dataBody></dataBody>
</ACK>
</dataBody>
</GENERIC>
However, in some cases which happens usually on a daily basis we get ACK errors to the similar submitted messages, for example
<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/11.11.11.11:55888 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Fri Nov 17 19:35:00 EST 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="43881" dataSize="65">
<extendedHeader data="0100"/>
<dataBody>
<POST domainType="MARKET_PRICE" streamId="5" containerType="MSG" flags="0x62 (HAS_POST_ID|POST_COMPLETE|ACK)" postId="43880" postUserId="0" postUserAddr="0.0.0.0" dataSize="43">
<dataBody>
<UPDATE domainType="MARKET_PRICE" streamId="5" containerType="FIELD_LIST" flags="0x08 (HAS_MSG_KEY)" updateType="0" dataSize="21">
<key flags="0x02 (HAS_NAME)" name=".SOMERIC"/>
<dataBody>
<fieldList flags="0x08 (HAS_STANDARD_DATA)">
<fieldEntry fieldId="6" data="0C16 90"/>
<fieldEntry fieldId="16" data="120B 07E7"/>
<fieldEntry fieldId="18" data="0023"/>
</fieldList>
</dataBody>
</UPDATE>
</dataBody>
</POST>
</dataBody>
</GENERIC>
<!-- java.nio.channels.SocketChannel[connected local=/11.11.11.11:55888 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Fri Nov 17 19:35:05 EST 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="43883" dataSize="31">
<extendedHeader data="0100"/>
<dataBody>
<ACK domainType="MARKET_PRICE" streamId="5" containerType="NO_DATA" flags="0x22 (HAS_TEXT|HAS_NAK_CODE)" ackId="43880" nakCode="INVALID_CONTENT" text="Invalid content" dataSize="0">
<dataBody></dataBody>
</ACK>
</dataBody>
</GENERIC>
As it can be seen we send messages with the identical format/structure but sometimes get
nakCode="INVALID_CONTENT" text="Invalid content"
as ACK message.
We are not able to identify the cause of INVALID_CONTENT ACK error messages as from our point of view the outgoing message format is the same and valid.
Any help to get the reason of the problem is highly appreciated.
Best Answer
-
Thank you for reaching out to us.
I ran the application to submit the same message to RCC and I got the ACK message properly. However, I sent this post message to the test RIC: TRCCTEST02.
<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/10.29.185.239:6132 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Tue Nov 21 12:23:21 ICT 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="29" dataSize="68">
<extendedHeader data="0100"/>
<dataBody>
<POST domainType="MARKET_PRICE" streamId="6" containerType="MSG" flags="0x62 (HAS_POST_ID|POST_COMPLETE|ACK)" postId="28" postUserId="0" postUserAddr="0.0.0.0" dataSize="46">
<dataBody>
<UPDATE domainType="MARKET_PRICE" streamId="6" containerType="FIELD_LIST" flags="0x08 (HAS_MSG_KEY)" updateType="0" dataSize="21">
<key flags="0x02 (HAS_NAME)" name="TRCCTEST02"/>
<dataBody>
<fieldList flags="0x08 (HAS_STANDARD_DATA)">
<fieldEntry fieldId="6" data="0C16 90"/>
<fieldEntry fieldId="16" data="120B 07E7"/>
<fieldEntry fieldId="18" data="0023"/>
</fieldList>
</dataBody>
</UPDATE>
</dataBody>
</POST>
</dataBody>
</GENERIC>
<!-- Incoming Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/10.29.185.239:6132 remote=contrib1-emea1.platform.refinitiv.com/99.81.199.166:443] -->
<!-- Tue Nov 21 12:23:21 ICT 2023 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<GENERIC domainType="SYSTEM" streamId="3" containerType="MSG" flags="0x19 (HAS_EXTENDED_HEADER|HAS_SEQ_NUM|MESSAGE_COMPLETE)" seqNum="29" dataSize="14">
<extendedHeader data="0100"/>
<dataBody>
<ACK domainType="MARKET_PRICE" streamId="6" containerType="NO_DATA" flags="0x00" ackId="28" dataSize="0">
<dataBody>
</dataBody>
</ACK>
</dataBody>
</GENERIC>I also found that you have submitted a ticket to the RCC support team to verify what problem is.
I will update this information in the ticket so the support team can verify this issue on the server side.
0
Answers
-
Thank you @Jirapongse. However, It is still not clear what causes the error as I am still waiting for the answer from RCC support team.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛