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?
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