127.0.0.1 in EMA status message
If see the following messages (related to the DACS mount configuration), where is the 127.0.0.1 from? e.g., the DACS host or the (docker with real ip) host running the application?
State: Closed/Suspect/Maximum logins reached - text: "Access Denied-already using position 127.0.0.1"
Best Answer
-
Hi @Frederic
When the code sends a LOGIN request message, they should specify the IP Address/hostname of the PC/server where the application is running. If they do not provide the actual details, it defaults to 127.0.0.1 (localhost). So, they need to change their code to send the correct details - then the error will show that address.
e.g.
OmmConsumer consumer( OmmConsumerConfig().host( "yourads:14002" )
.username( "user" ).position("129.121.1.2/net") );where 129.121.1.2 is the local IP address or hostname.
NOTE: just to clarify EMA sends a LOGIN behind the scenes and the above call changes the position attribute in that Login. If the developer is explicitly sending an MMT_LOGIN, they should change the Position in that (e.g. consumer example 420_MP_AdminDomainCfg)
0
Answers
-
Hi @Frederic
This means that an application is already logged in using the same DACS ID on a different PC/server.
There is a limit set in the DACS system regards how many mounts can be made with a DACS ID - by default, this is set to 1.
This can be increased using the DACS admin system - however, there is often additional data usage cost associated with allowing multiple mounts with a single ID.
The developer should speak to their local DACS admin team.
0 -
Yes that's true, the mount is configured with low number. However, where is the 127.0.0.1 from? i.e., the logic to determine the ip address? 127.0.0.1 is ambiguous0
-
Is the 127.0.0.1 means the DACS server? or a host says he is '127.0.0.1'?
0 -
@umer.nalla By the way, for multiple EMA consumers in one application (1 process with threads), will that be counted as multiple 'mount's or just 1 'mount'?0
-
Many thanks for the clarification.0
-
@umer.nalla For docker instances running on the same PC, is that OK to share one user (so as one mount)?0
-
Hi @Frederic - in theory, that sounds OK - but I don't know enough about our content licencing to confirm if that would be OK or not.
I expect you would need to speak to a Data licencing specialist within Refinitiv.
0 -
Gotcha and many thanks, yes it should be decided by the licensing team, although in this case it's docker.0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛