Murex unable to connect to ADS using WelbSocket
Our client is trying to set up Murex to connect to ADS using WebSocket (port 15000). Although they are able to telnet on the port to the ADS, Murex shows an error as attached. murex_14Apr.pngmurex_telnet 14April.pngUpdated Log.zip
Best Answer
-
Hi @MayurC,
Their ADS does not support this QoS. Please ask the client to not send the QoS information in the request message, and form it like this:
{
"Type": "Request",
"ID": 3,
"Domain": "MarketPrice",
"View": [
"BID",
"ASK",
"HIGH_1",
"LOW_1",
"PROD_PERM",
"RDNDISPLAY",
"RECORDTYPE"
],
"Key": {
"Service": "h03tcEDD",
"Name": "EUR="
}
}2
Answers
-
Thanks for reaching out to us.
I checked the log file and found that the client may use RFA.
RFA doesn't support WebSocket connections. The client needs to use Refinitiv Real-Time SDKs to support WebSocket connections. Otherwise, you can develop applications with any programming language that supports WebSocket. The client can refer to the examples on GitHub.
I hope that this information is of help.
0 -
Hi,
Murex team confirm they are sending JSON messages and are not using RFA. Attached are more files as reference.
On 31-April, they did get successful connection (success.txt) to ADS using same properties file but it gave QOS error. Hence, they disabled QO on Murex server after which it did not connect back and always shows the error as attached file (error.txt) .
Attached is the properties file (rmd-trep-omm) and overall application logs (logs.txt) for reference.
Kindly share findings.
0 -
The log shows the java.lang.NullPointerException at the following line.
java.lang.NullPointerException: null
at murex.connectivity.rmdtrepomm.core.RmdTrepOmmRfaConfiguration.<init>(RmdTrepOmmRfaConfiguration.java:209) ~[rmd-trep-omm-managed-interface-core-51.1.1.jar:?]
at murex.connectivity.rmdtrepomm.core.RmdTrepOmmRfaConfiguration.createOverriddenConfig(RmdTrepOmmRfaConfiguration.java:338) ~[rmd-trep-omm-managed-interface-core-51.1.1.jar:?]
at murex.connectivity.reuters.rfa.component.omm.RfaOmmConnectorManager.getOrCreateConnector(RfaOmmConnectorManager.java:169) ~[rfa-managed-connector-component-51.1.1.jar:?]
at murex.connectivity.reuters.rfa.component.omm.RfaOmmConnectorManager.getOrCreateConnector(RfaOmmConnectorManager.java:146) ~[rfa-managed-connector-component-51.1.1.jar:?]You need to contact the developer who develops this code to investigate this issue.
0 -
hi,
Below request received from Murex team while testing via our Websocket API call. Is this something is Refinitv configure/setup on dedicated ADS.
Is it possible for Refinitiv to set "SupportsQoSRange" for Websocket API service h03tcEDD at server 159.43.84.39 side, to avoid "No multiple qos service supports this QoS." ?
Because Murex connector is sending :
{"Type":"Request",
"Qos":
{"Dynamic":true,
"Rate":"TimeConflated",
"Timeliness":"Realtime"},
"WorstQos":
{"Dynamic":true
,"Rate":"TimeConflated"
,"Timeliness":"Realtime"},
"ID":3,
"Domain":"MarketPrice",
"View":
["BID","ASK","HIGH_1","LOW_1","PROD_PERM","RDNDISPLAY","RECORDTYPE"],
"Key":
{"Service":"h03tcEDD",
"Name":"EUR="}}
but received :
[
{
"ID": 3,
"Type": "Status",
"Key": {
"Service": "h03tcEDD",
"Name": "EUR="
},
"State": {
"Stream": "Closed",
"Data": "Suspect",
"Code": "NoResources",
"Text": "No multiple qos service supports this QoS."
}
}
]0 -
Murex are now geting the below error while using refinitiv’s websocket tryitnow browser :
No multiple qos service supports this QoS.
Pl advice.
SENT:
{
"Type": "Request",
"Qos": {
"Dynamic": true,
"Rate": "TimeConflated",
"Timeliness": "Realtime"
},
"WorstQos": {
"Dynamic": true,
"Rate": "TimeConflated",
"Timeliness": "Realtime"
},
"ID": 3,
"Domain": "MarketPrice",
"View": [
"BID",
"ASK",
"HIGH_1",
"LOW_1",
"PROD_PERM",
"RDNDISPLAY",
"RECORDTYPE"
],
"Key": {
"Service": "h03tcEDD",
"Name": "EUR="
}
}
RECEIVED:
[
{
"ID": 3,
"Type": "Status",
"Key": {
"Service": "h03tcEDD",
"Name": "EUR="
},
"State": {
"Stream": "Closed",
"Data": "Suspect",
"Code": "NoResources",
"Text": "No multiple qos service supports this QoS."
}
}
]
0
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 中文论坛