TREP: Unexpected "Output threshold breached for <user>...."

Hi,
I developed a JAVA application based on Refinitiv Realtime SDK, that is consuming RICs on TREP.
Today, one of my customer reporting an issue that he was able to observe many time during the night:
- my application is disconnected from TREP
- ADS logs shows errors such as
Output threshold breached for XXX" at position "12.23.45.78/abcdef" on host "thehost" and port number "12345" using application "256"
According to what I can read, it seems that my application does not consum RICs fast enough. However:
- at this time, the activity is not so huge (client think "only" around 1000 RICs per seconds)
- but during the day, the application is able to work easily with an activity (according to the client) around 4000 RICs per seconds
So there is apparently no reason why my application would not be able to consum the stream
According to your knowledge and your experience, what could be the reason of the error my client is having?
Is it possible to tune the "EmaConfig.xml" (or my java code) in order to avoid this error (or at least to reduce the risk it occurs)
Thank you
Regards,
Philippe
Answers
-
Thank you for reaching out to us.
Typically, this error indicates that the output buffers used by this connection breached. It could be a slow consumer or network issue. You may increase the number of output buffers via the ADS configurations. The current settings may be too low.
!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ! ! *ads*"${port}"*guaranteedOutputBuffers : 200 !#help ! guaranteedOutputBuffers: { 1 - N buffers } ! ! The number of output buffers guaranteed per channel. ! ! Default value: 24 !#end !++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ! ! *ads*"${port}"*maxOutputBuffers : 400 !#help ! maxOutputBuffers: { 1 - N buffers } ! ! The maximum number of output buffers to allocate per channel. ! The (maxOuputBuffers - guaranteedOutputBuffers) defines the number of ! buffers to be dynamically created to be requested as needed from the pool ! per channel. Mounts will initially be allocated the guaranteedOutputBuffers ! and can take more from the buffer pool as needed until they reach the ! maxOutputBuffers limit. ! ! Default value: 48 !#end !++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
However, to investigate this issue on the application, you may need to contact the API support team directly via Contact Premium Support.
0 -
Hi
Our problem regarding the buffer overflow is not yet solved.
By adding logs in our application, we realized few things:
- the problem always occurs at midnight UTC
- the minute before the issue (i.e. before midnight UTC) the number of updates per seconds strangely starts to grow
- just before the overflow, many RICs are updated many times per seconds
- client has between 14000 and 16000
- I strongly suspect that many updates are identical
- one minute before the throughput was around 1000 updates per seconds ⇒ it suddenly grows to more than 10.000 updates per seconds!!!
Can you please help me to understand what happens
Regards,
Philippe
0 -
According to the information, it could be a slow consumer that causes the buffer overflow on the server side.
EMA is used to subscribe to items and retrieve data from the server. You may need to contact the content support team directly via MyAccount to verify the retrieved content.
Did you subscribe to an item more than once? For example, if the application subscribes to IBM.N twice, EMA will fanout a retrieved update message so it means that the application will receive the same update message twice.
Can share the sample RICs, identical updates, and timestamps (including timezone)?
I can check the data from our Tick History database.
0 -
Hello
According to the information, it could be a slow consumer that causes the buffer overflow on the server side.
really? our feeling is that the consumer (i.e. my software) is flooded by many events. OK my software does not succeed to consume them fast enough but for me the real question is "why so many events and overall why exactly at midnight UTC?"
Did you subscribe to an item more than once? For example, if the application subscribes to IBM.N twice, EMA will fanout a retrieved update message so it means that the application will receive the same update message twice.
My application is not supposed to subscribe twice a market data but I will investigate in this direction; thank you for the advice
Can share the sample RICs, identical updates, and timestamps (including timezone)?
OK, when I'll have time I'll build a sample and we'll try to run it on client site
I can check the data from our Tick History database.
what to you mean? I don't understand?
Thank you for helping
Best regards,
Philippe
0 -
Why so many events and overall why exactly at midnight UTC?
You need to contact the content support team to verify this behavior.
If I know RICs, data, and times, I can check if the data was really from the data feed. I can access the Tick History database to verify the data.
0
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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛