question

Upvotes
Accepted
paul.cockerham avatar image
1 ●0 ●1 ●1

TRCC postMsg NAK when using containerType RSSL_DT_OPAQUE

We have an application team who are unable to publish via an ads on the TRCC TREP service with their RFA 6 C++ application

We see the following in adh.dbg:

[Thu Aug 05 12:50:14 2021] RSSL Message Of Length 160 Sent on Socket 44

<!-- rwfMajorVer="14" rwfMinorVer="1" -->

<genericMsg domainType="RSSL_DMT_SYSTEM" streamId="3" containerType="RSSL_DT_MSG" flags="0x19 (RSSL_GNMF_HAS_EXTENDED_HEADER|RSSL_GNMF_HAS_SEQ_NUM|RSSL_GNMF_MESSAGE_COMPLETE)" seqNum="7" dataSize="143">

<extendedHeader data="0100"/>

<dataBody>

<!-- rwfMajorVer="14" rwfMinorVer="1" -->

<postMsg domainType="RSSL_DMT_MARKET_PRICE" streamId="1" containerType="RSSL_DT_OPAQUE" flags="0x66 (RSSL_PSMF_HAS_POST_ID|RSSL_PSMF_HAS_MSG_KEY|RSSL_PSMF_POST_COMPLETE|RSSL_PSMF_ACK)" .....

and later the NAK message....

<ackMsg domainType="RSSL_DMT_MARKET_PRICE" streamId="1" containerType="RSSL_DT_NO_DATA" flags="0x22 (RSSL_AKMF_HAS_TEXT|RSSL_AKMF_HAS_NAK_CODE)" ackId="55" nakCode="RSSL_NAKC_DENIED_BY_SRC" text="PostMsg has not have container type of RSSL_DT_MSG"


How easy is it for them to change their postMsg containerType from RSSL_DT_OPAQUE to RSSL_DT_MSG? As mentioned their application is coded using RFA6 C++

treprfarfa-apipostingcontributionsrcc
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

4 Answers

Upvotes
Accepted
umer.nalla avatar image
20.3k ●73 ●10 ●20

Hi @paul.cockerham

Ok - so this is looking more like an issue with the ADS conversion from SSL Insert to RSSL Post.

I can't think of anything they can do differently in their RFA 6.0 code to affect that.

Most likely there is an issue with the ADS or ADH configuration or compatibility issue between RFA6 and whichever version of ADS you are using.

I recommend you raise a My.Refinitiv ticket for Refinitiv Real-Time Advanced Distribution Server product - to discuss your issue with one of our RTDS specialists.

I will do some more digging here and if I get anything useful I will post back here.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

paul.cockerham avatar image paul.cockerham

Many thanks Umer! I've raised the ticket with MyRefinitiv

Do you know what rmds.cnf service parameters are needed at a minimum to ensure correct ADS conversion from SSL Insert to RSSL Post?

Upvotes
umer.nalla avatar image
20.3k ●73 ●10 ●20

Hi @paul.cockerham

I cannot understand how it is being set to OPAQUE in the first place.

Are they setting the payload of the PostMsg as a FieldList or some other data structure?

If they have not already done so, they should download a recent version of RFA and study the StarterConsumerPost example which demonstrates how to submit a Post using RFA.

Downloads | Refinitiv Developers

The other key thing to note here is that we stopped supporting RFA 6.0 a long time ago. The oldest version of RFA C++ we support is RFA 7.7. So, it could well be an incompatibility between RFA 6 and the ADS.

If they are writing a new Posting application then they should ideally be using EMA (C++ or Java) - much simpler to code. It takes just a few lines of code to connect to the server and create + submit a Post Msg compared to several hundred lines for the RFA C++ equivalent.

Contributing your data to Refinitiv | Refinitiv Developers


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

umer.nalla avatar image umer.nalla
The other thing I should add is that EMA supports direct contribution to RCC - so future-proofing if they ever decide to bypass the ADS.
paul.cockerham avatar image paul.cockerham
Thanks Umer

If it helps their application can contribute via mlip connection (dataType 2) on TREP but not via TRCC. They are trying to meet the mlip EOL deadline by end of Sep 2021 and are attempting to migrate to TRCC before then. Is there a way for them to meet the migration deadline using their current RFA 6 code or must they move to a later version do you think?

Upvotes
umer.nalla avatar image
20.3k ●73 ●10 ●20

Hi @paul.cockerham

Is the RFA 6 app using MarketFeed SSL connectivity or RSSL/RWF connectivity?

I assumed from your above post that it was RSSL - but as you mentioned it works with MLIP, I am now wondering if the ADS is doing the conversion from SSL Insert to RSSL Post and something is going wrong in the conversion?



icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

paul.cockerham avatar image paul.cockerham

Yes, they are using a MarketFeed SSL connection.

Protocol 6, ssl4.0be


From ads.dbg:

Sipc message Received: Len: 128 HdrLen: 6 Flags: 0 ProtId: 0 FD: 32

Thu Aug 05 12:52:56 2021

MsgLen 128 Flags 0 Opcode 24 HdrLen 5

SSL Insert Request. srvcId: 2 ReqId: 215386792


and later...


Sipc message Sent: Len: 83 HdrLen: 6 Flags: 0 ProtId: 2 FD: 32

Thu Aug 05 12:52:56 2021

MsgLen 83 Flags 0 Opcode 23 HdrLen 5

SSL Insert Nak: srvcId: 2 ReqId: 215386792 Code: 2



Upvotes
umer.nalla avatar image
20.3k ●73 ●10 ●20

Hi @paul.cockerham

The moderators on this forum are APIs specialists and whilst some of us have some understanding of the RTDS system, you will need to ask the RTDS team for the required parameters.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea