EMA Java - idle consumer disconnecting
As a temporary workaround for issue mentioned here https://community.developers.refinitiv.com/questions/28182/ema-ommconsumer-memory-leak-in-java-api.html we implemented a pool of consumers. It works, but now we faced another issue:
When the consumer sits idle in the pool it eventually disconnects from Reuters and when we eventually want to use it and query some data, we receive errors for few first attempts:
"Open / Suspect / None / 'Service not up'"
then for few next calls:
"Open / Suspect / None / 'Service not available'"
and then at some moment we start receiving actual data for all following calls, until we stop requesting data and consumer goes to idle state again for some time, in which case the whole scenario repeats.
We increased ConnectionPingTimeout parameter to 5 minuts, but then we have just a new limitation of 5 minutes for idling the consumer.
Since this parameter name is referring to "ping" I was expecting there is a "ping" going on behind the scene, but it turns out it's not (or is it?), so we implemented our own "kind of" ping mechanism, where we request snapshot data for one symbol every interval.
It's working, but it's far from ideal.
Is there a more appropriate way to keep the idle consumer "alive"?
Best Answer
-
Based on the client given information, the application has multiple users. The application creates a new consumer every time when user requested data and then dispose the consumer. This is possible the root cause of this issue.
The client reported that somehow memory allocated for consumer was not freed and the application were quickly running out of memory. The API 3rd level support team has investigated the issue and found the following information:Normally, a memory usage can grow over time until JVM performs a garbage collection. So, the customers need to monitor the application in long run to check the graph if the usage level drops and makes it looks like a zig-zag pattern or not. If there is a memory leak potential, the zig-zag pattern will also slope up as well.
0
Answers
-
Hello @pawel.salawa
Since this problem requires deep investigation from Elekron API specialist team(my team), please refer to my answer in the your previous question, EMA OmmConsumer memory leak in Java API? how to allow my team to support your query.
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 中文论坛