Offstream post returns Error Text channel out of buffers errorId=-4 errorText=channel out of buffers
Creating an offstream post for > 5000 instruments fails with
Error Text channel out of buffers errorId=-4 errorText=channel out of buffers.
For a long running application that takes post requests an OmmConsumer is created
A login is requested and after the Login refresh message 5000 post messages are triggered
after each post the PostMsg is cleared.
Then we get
Error Text channel out of buffers errorId=-4 errorText=channel out of buffers
The Guranteed buffer size is set to 5000 in Ema config.
Best Answer
-
Hello @niz,
As you appear to run out of guaranteed buffer space per your channel, my point was, to try to determine the reasonable setting for your custom posting consumer. There is no max supported number- see EMA Configuration Guide. This number times maxFragmentSize will be the buffer space in bytes available for your connected channel. Keeping large unnecessary buffers is wasteful, and may lead to consumer being slow, so usually we gauge the config required against the app requirements.
Running out of the buffer space is undesirable, but will not result in a memory leak, rather, in the more recent versions of SDK ( are you on 1.5 or 2.0? that would be preferable as many important fixes has been applied since the older versions), it just results in an error that you have seen.
Are you able to adjust and to proceed?
0
Answers
-
Hello @niz,
I would try to tune config for the use case, by first succeeding on a smaller post, and then making work the larger post that you require. I would post the same fields for a single instrument, and make sure the post succeeds. Once the post succeeds, grow by increment. Once you narrow down where the post starts failing, you may wish to increase the guaranteed output buffers to make sure the request succeeds again, till you arrive at the required 5000 instruments posted successfully.
There is a possibility, although less likely, because in this case you see the specific error message on the lack of acknowledgement, that this may be related to the recipient of the post, the recipient (custom provider or infra?) needs to support posting, and this specific post needs to be acknowledged by the recipient as valid.
0 -
Thanks, 5000 is not the required, the number could be more, so shall we then have a max supported number?
Also if the same consumer is being used subsequent requests with the same amount accumulate and the guaranteed value is no longer enough, could this be a memory leak?
0 -
will Run some test cases and evaluate, thanks
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 中文论坛