How to prevent downloading RWFTEST1
dsystemdesktopando新しいフォルター.zip
We are trying to get feedname=hEDD through RTBS, and at the same time this starts to get RWFTEST1.
However, we don't need this RWFTEST1 and prevent downloading because this downloading results in error.
Can we skip or prevent downloading this RWFTEST1?
Please let us know how to.
Please see below for the error message.
RWFTEST1
>2017-03-27 07:24:20,430 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.directory.DirectoryDataClient : INFO - [RWFTEST1]: Dictionaries Provided = [RWFFld, RWFEnum]
>2017-03-27 07:24:20,430 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.directory.DirectoryDataClient : INFO - [RWFTEST1]: Dictionaries Used = [RWFFld, RWFEnum]
hEDD
>2017-03-27 07:24:20,432 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.directory.DirectoryDataClient : INFO - [hEDD]: Dictionaries Provided = [RWFFld, RWFEnum]
>2017-03-27 07:24:20,432 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.directory.DirectoryDataClient : INFO - [hEDD]: Dictionaries Used = [RWFFld, RWFEnum]
>2017-03-27 15:41:47,566 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.dictionary.OmmFieldDictionaryFacility$OMMFieldDictionaryClient : INFO - Received dictionary info update on RWFFld
>2017-03-27 15:41:47,567 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.dictionary.OmmFieldDictionaryFacility$OMMFieldDictionaryClient : WARN - Incorrect data type received: payload data is 128/NO_DATA instead of 138/SERIES
>2017-03-27 15:41:47,569 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.dictionary.OmmFieldDictionaryFacility$OMMFieldDictionaryClient : INFO - Received dictionary info update on RWFEnum
>2017-03-27 15:41:47,569 [RFA-Dispatcher] murex.interfaces.provider.reuters.service.impl.omm.dictionary.OmmFieldDictionaryFacility$OMMFieldDictionaryClient : WARN - Incorrect data type received: payload data is 128/NO_DATA instead of 138/SERIES
>2017-03-27 15:41:52,403 [RtbsPublisherQueueMonitor] murex.apps.datalayer.spi.rtbs.impl.DriverProtocolImpl : INFO - RTBS publisher queue state: received: total=0 last=0 sent: total=0 last=0 dropped: total=0 last=0 queued: 0
>2017-03-27 16:37:47,265 [DriverProtocolReceiveThread] murex.interfaces.provider.reuters.service.impl.RfaRealtimeConnectorImpl : ERROR - This is fatal.
>2017-03-27 16:37:47,265 [DriverProtocolReceiveThread] murex.interfaces.provider.reuters.service.impl.RfaRealtimeConnectorImpl : ERROR - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>2017-03-27 16:37:47,265 [DriverProtocolReceiveThread] murex.interfaces.provider.reuters.service.impl.RfaRealtimeConnectorImpl : ERROR - Notify listener for fatal exception: Reuters RFA session initialization failed.
>2017-03-27 16:37:47,265 [DriverProtocolReceiveThread] murex.realtime.provider.reuters.rtbs.RfaRTBSDataSource : FATAL - Reuters Realtime Connector failed with fatal exception:
>murex.interfaces.provider.reuters.domain.RfaException: Reuters RFA session initialization failed.
>。。。Caused by: murex.interfaces.provider.reuters.domain.RfaException: Failed fetching dictionary data for service RWFTEST1.
Best Answer
-
Hello @Hirou_Tanaka
There is no RFA configuration for OMM applications about downloading dictionary; all is done by the application. Hence, you should contact Murex support team to ask how to configure Murex application or which command line can set the application not to request dictionary from RWFTEST1.
0
Answers
-
We are getting this message also but I don't think I can ask Murex this question - we don't use their's software - we are competotors...
0 -
Hello @boris
RFA does not provide configuration about downloading dictionary. This is done by application. Hence, you should contact the team who develops this application.
0 -
I developed this application. I can look at a mirrow and talk to myself of course:)
When people from different companies complaining about same issue, maybe someone should look at his own system rather than keep pushing back.
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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛