[EMA][C++] Login Re-Issue failed
Hi,
While doing component failovers in my application, i noticed following error (I am using realtime sdk - ema api/). What does that mean? What should i do to avoid these errors. (As it seems, login re-issue has been successful in second attempt)
Failed to reissue login request. Reason: RSSL_RET_INVALID_DATA. Error text: Login userNameType does not match existing request.
I noticed following in the documentation. We haven't handled following errors in our application explicitly. Has it anything to do with it ?
HTTP Error Handling for Reactor Token Reissues
The Enterprise Message API supports handling for the following HTTP error codes from the API gateway:
300 Errors:
- Perform URL redirect for 301, 302, 307 and 308 error codes.
- Retry the request to the API gateway for all other error codes
400 Errors:
- For Version 1 authentication, retry with username and password for error codes 400 and 401
- Stop retry the request for error codes 403, 404, 410, and 451
- Retry the request to the API gateway for all other error codes
500 Errors: Retry the request to the API gateway for all error codes
Best Answer
-
Did the application call the reissue method with the Login handle?
For example:
consumer->reissue(Login::LoginReq().name("user").getMessage(), loginHandle);
I got the following error when running the above code.
0
Answers
-
Thank you for reaching out to us.
The error mean that the userNameType in the login request message doesn't match the previous login request. Typicallly, the userNameType in the login request message must be the same.
Please let us know the version of the Real-Time SDK that you are using.
Moreover, you have mentioned "doing component failovers in the application". How did you do it?
0 -
Thanks for the response @Jirapongse
I am using ema3.6.6.L1. I have a primary process and a mirror process. Whenever primary process is down, mirror takes over and connect with RTO.
0 -
Thanks for the hint @Jirapongse, I'll check on that path. Apparently correct login handle has been used. I noticed, nameType field is set in login message as well as set (programmatically) it in consumer configurations.
m_loginHandle = m_consumer->registerClient(*loginReqMsg,*this, 0);
------
refinitiv::ema::access::ReqMsg* loginReqMsg = m_emaMessageHandler->getLoginReqMessage();
loginReqMsg->initialImage(false);
loginReqMsg->interestAfterRefresh(true);
loginReqMsg->pause(isInputPause);
m_consumer->reissue(*loginReqMsg, m_loginHandle);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 中文论坛