RSSL buffer failed
Has anyone come across this error ? It appears every time when traffic volume is high, RFA got disconnected and got this error. Any hint to indicate what might be the issue ?
INFO (FA_LOG) Publisher 0: OMM error event received: Attempt to get rssl buffer failed! Please check log for details. Client session could have already disconnected.
Best Answer
-
When publishing a message, the message is written to the internal
buffer before sending it to the network. This buffer is reserved when the
channel is created and its size can be configured by using the following RFA
configurations for RSSL_PROV connection type.- bufferPoolSize
Sets the maximum size of the buffer pool, which is
shared among all server-side RSSL channels. Each RSSL Server can have its own
buffer pool
- guaranteedOutputBuffers
Number of output buffers that are guaranteed to an
RSSL channel. Once this value is reached, the channel will start using pool
buffers, if available. Guaranteed output buffers are allocated on a per channel
basis
- maxOutputBuffers
Maximum number of output buffers allowed to an RSSL
channel on the server side. This is the number of guaranteed output buffers
plus the number of pool buffers available to this channel
Once this value is reached, the channel will be
unable to get any new buffers until some of the currently held buffers are
released
This error “Attempt to get rssl buffer failed!”
indicates there are no buffers available to the API. This typically occurs
because:- The channel has been disconnected
- The network issue
- The client application is a slow consumer
0 - bufferPoolSize
Answers
-
"Attempt to get rss buffer failed!".
I wonder what "rss" is or if that is just a spelling error ? Btw: You haven't specified which of the RFA APIs you are using (C++, Java, .NET).
0 -
sorry typo should be rssl buffer. API is using C++
0 -
Hi,
There was a bug in RFA C++ 7.2 that was fixed in RFA C++ 7.4.0.L1 as described below:
rfasl10803;Provider may not get InactiveClientSession event when consumer is killed The provider application may not able to get InactiveClientSession event when the consumer application is killed. If the application still publishes data to inactive client, a lot of the error message "Attempt to get rssl buffer failed! Please check log for details. Client session could have already disconnected" are generated in rfa log file.
Can you confirm which version of RFA C++ you are using?
Regards,
Umer0
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 中文论坛