PubErrorEvent: Failed to publish the market data event to SAPI

Best Answer
-
The SAPI is the underlying layer in RFA that
handles network connection (SSLED_MP connection) between the RFA
MarketDataManagedPublisher and its clients. The PubErrEvent could be generated once SAPI could not write the message to the
network with a specific reason.Below are some possible scenarios.
- Image is published with status other than “Ok” or
“Stale”SAPI allows only two types of status
for image: Ok or Stale status. Other statuses, for example, “NoChanged” status
means the state is the same as before which makes sense in term of an update
but not an image.- There is not enough buffer for SAPI to send message to
networkRFA provide configuration parameter “outputBuffers” to tune this
output buffer. For more detail, see RFA Configuration Guide provided in RFA
package.You may try following parameter to isolate the issue.
\Connections\Connection_SSLED_MP\outputBuffers = 100000000
If the scenarios listed above do not occur in your applicaiton, please provide further information such as reproduction steps, published messages.
0
Answers
-
Hi @iain.cadman
If it is happening consistently on live system and you cannot recreate in test environment, then my immediate thought would be that there is some difference in the TREP config between your test and live environment. Or a difference in versions of TREP components between test and live?
Can you provide a few more details on what you are trying to do, publisher type, connection type? Can you recreate using one of our example apps?
0 -
Thanks for the response. I am seeing this on a customer site, so there will likely be a difference in components and configuration.
These messages only occur when the contributor program is being loaded tested. The publicationID on the error event is a long way behind that reported for a publish done around the same time.
I will increase the buffers as suggested and see if this has an effect. I suspect, though, that increasing the buffers will only delay the problem.
0 -
Yes, increasing the buffers will only delay the problem. If the parameter has an effect, the issue needs to be investigated further as there might be bottlenect on transport layer.
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
- 24 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
- 713 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 中文论坛