Why consumer application receives OMMMsg.MsgType=STATUS_RESP from RFA after it sucess connect to ADS

Our application uses RFA Java API to consume data from ADS.
We notice that after connected to ADS, looks like our application gets the event OMMMsg.MsgType=STATUS_RESP as follows:
MESSAGE
Msg Type: MsgType.STATUS_RESP
Msg Model Type: LOGIN
Indication Flags:
Hint Flags: HAS_ATTRIB_INFO | HAS_STATE
State: OPEN, OK, NONE, "Login accepted by host ads123456"
However, the RSSL trace shows that it receives MsgType=REFRESH_RESP from ADS.
The application is working fine but we want to know is it an expected behavior?
Best Answer
-
This is an expected behavior of the RFA Java API since version 7.0. When a Login request is sent to RFA by the user, the user application will immediately get a REFRESH_COMPLETE Refresh response message with a stream state of OPEN and a data state of SUSPECT (“State: OPEN, SUSPECT, NONE, "All connections pending"”) from the API. Upon acceptance of a Login Request, RFA consumer applications will get a Status message on the Login Stream when a state change occurs to the aggregated Login stream.
Applications using RFA Java 7.0 and above will no longer get Refresh response messages when a Login stream request has been satisfied on a per connection basis. After the initial Refresh response message with stream state OPEN data state SUSPECT, the application should expect Status messages on the Login stream only when the aggregate changes.
Please
see more detail regarding this behavior in the following documents:- API
Migration Guide section “From 6.5.0 to 7.0.0 or later”. This document is available
at <RFA Java Package>\Docs\portal\ api_migration.htm file - Section
3.4.2 “Initial Login” of the RFA Java RDM Usage Guide document. This document
is available at <RFA Java Package>\Docs\RFAJ_RDMUsageGuide.pdf file
0 - API
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛