LPC "Unable to get RIPC client buffer"

Hi,
We are consistently getting the below error from LPC (Legacy Protocol Converter) for one of our users. After the error, no live prices are available to that user. Things are working fine for other users:
Disconnecting secure channel secureChannel.146. Disconnecting user socket 18 from host 10.8.193.234. Reason: Unable to get RIPC client buffer to send message. ErrorId: -4 Error: </local/jenkins/workspace/RRTLPC/OS/OL7-64/esdk/source/esdk/Cpp-C/Eta/Impl/Transport/rsslSocketTransportImpl.c:1429> Error: 1009 ipcDataBuffer() failed, out of output buffers. The output buffer may need to be flushed.
Is anyone able to shine some light on what this might be, and how we might go about fixing it, please?
Thanks in advance,
David.
Best Answer
-
Thanks for reaching out to us.
The API used by LPC encodes the data into the output buffer before sending the data in the buffer to the network. The API reserves the number of output buffers when it starts.
The error indicates that the API was unable to send the data to the network and it used all reserved output buffers.
Typically, it could be a network issue or the client application is a slow consumer.
For more information, you need to contact the LPC support team directly via MyRefinitiv to investigate this issue.
I hope that this information is of help.
0
Answers
-
An LPC restart fixed things, for now. Would be good to understand what the problem was though, if anyone has any thoughts.
0 -
@Jirapongse. I've entered a ticket with MyRefinitiv and am awaiting a response. Interestingly, we restarted the client PC more than once but the same problem kept occurring until we restarted LPC itself.Thanks for getting back to me0
-
Thanks @Jirapongse. The LPC support team pointed me to section 2.3.1 of the LPC manual which suggests tweaking TCP buffer settings as follows:
net.core.rmem_max = 8388608
net.core.wmem_max = 8388608
net.core.rmem_default = 4194304
net.core.wmem_default = 4194304
net.ipv4.tcp_rmem = 4096 4194304 8388608
net.ipv4.tcp_wmem = 4096 4194304 8388608
net.ipv4.tcp_mem = 4096 4194304 8388608I've made those changes and have not yet seen a reoccurrence of the problem.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛