Received GenericMsg on not established stream
Hi all. I'm building an OMM provider / consumer pair that swap generic messages based on samples StarterProvider_genericMsg and StarterConsumer_genericmsg. I'm converting the samples to use ValueAdd. My consumer works - It connects to the sample StarterProvider and the two happily swap messages all day long. The problem is with my ValueAdd provider: When I bring it up and connect my consumer, I get the following error:
CmdID : 5
Has SubmitClosure : False
Status : StatusText : OMMProvider::submit(...) received GenericMsg on not established stream. StatusTextW :
State : Failure
StatusCode : NoResources
So can anyone tell me what I'm not doing in my provider? How do I establish the stream at the provider?
Thanks
Best Answer
-
I assume that you are using RFA C++ or .NET. From the status text ,it looks like the provider submit message to stream which already closed. Please make sure that provider application properly manage client session and passing valid reqeust token when submit the message.
-Do you have any console output log from both Provider and Consumer side?
Since you have craeted a new Provider application based on our example, you may compare the codes and steps with original example.
Also you may turn on RSSL Tracing log on both Provider and Consumer side. It could help verify stream and message between Provider and Consumer. To turn on RSSL tracing log, please add the following config to Provider and Consumer connection
\Connections\<Connection_RSSL>\traceMsg = false
\Connections\<Connection_RSSL>\traceMsgToFile = true
\Connections\<Connection_RSSL>\tracePing = true
\Connections\<Connection_RSSL>\traceMsgFileName = "<RSSL Consumer/Provider Trace file name>"
\Connections\<Connection_RSSL>\traceMsgDomains = "all"
\Connections\<Connection_RSSL>\traceRespMsg = true
\Connections\<Connection_RSSL>\traceReqMsg = true
\Connections\<Connection_RSSL>\traceMsgHex = false
\Connections\<Connection_RSSL>\traceMsgMaxMsgSize = 200000000
\Connections\<Connection_RSSL>\traceMsgMultipleFiles = true<Connection_RSSL> is the name of Provider or Consumer connection in RFA configuration file. RFA will generate xml file name from traceMsgFileName for example RSSLConsumerTrace_<pid>.xml.
0
Answers
-
I got this working. I hadn't set up the event stream with a request / response pair first.
That logging technique is very handy though, 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛