Error causes and avoidance methods
We tried to use EMA to retrieve data from ELEKTRON_DD using the RIC code 'JPY=', but encountered the following log error and were unable to obtain the data. We are using V2 for authentication. Could you please share what this error indicates, its cause, and possible solutions?
ーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーー
6 10, 2025 2:33:42 午後 com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
警告: loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_1
RsslReactor @19b843ba
RsslChannel @64ec96c6
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd
6 10, 2025 2:33:44 午後 com.refinitiv.ema.access.ChannelCallbackClient reactorChannelEventCallback
情報: loggerMsg
ClientName: ChannelCallbackClient
Severity: Info
Text: Received ChannelUp event on channel Channel_1
Instance Name Consumer_1_1
Component Version ads3.7.2.E2.linux.rrg 64-bit
loggerMsgEnd
Status : Closed / Suspect / Not found / '**The record could not be found'
6 10, 2025 2:34:15 午後 com.refinitiv.ema.access.ChannelDictionary processCallback
警告: loggerMsg
ClientName: ChannelDictionary
Severity: Warning
Text: RDMDictionary stream was closed with status message
streamId 3
Reason State: Closed/Suspect/None - text: "Login stream was closed."
loggerMsgEnd
Best Answer
-
Thank you for your response.
I provide the contents of the XML.
—————————————————————————————————————————————————————
<!-- rwfMajorVer="14" rwfMinorVer="1" --><REQUEST domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x04 (STREAMING)" dataSize="0">
<key flags="0x26 (HAS_NAME|HAS_NAME_TYPE|HAS_ATTRIB)" name=" " nameType="5" attribContainerType="ELEMENT_LIST">
<attrib>
<elementList flags="0x08 (HAS_STANDARD_DATA)">
<elementEntry name="ApplicationId" dataType="ASCII_STRING" data="256"/>
<elementEntry name="ApplicationName" dataType="ASCII_STRING" data="ema"/>
<elementEntry name="Position" dataType="ASCII_STRING" data="10.226.1.19/tmdiy010"/>
<elementEntry name="AuthenticationToken" dataType="ASCII_STRING" data="removed"/>
<elementEntry name="Role" dataType="UINT" data="0"/>
</elementList>
</attrib>
</key>
<dataBody>
</dataBody>
</REQUEST>0
Answers
-
Thank you for reaching out to us.
The "Status : Closed / Suspect / Not found / '**The record could not be found'" error typically indicates that the subscribed item is invalid.
To investigate this issue, please enable the XML trace log in the EMA. You can enable it via the EMA configuration (XmlTraceToStdout or XmlTraceToFile) in the consumer. For example:
<Consumer> <Name value="Consumer_4"/> <Channel value="Channel_4"/> <Dictionary value="Dictionary_1"/> <MaxDispatchCountApiThread value="6500"/> <MaxDispatchCountUserThread value="6500"/> <XmlTraceToStdout value="0"/> <XmlTraceToFile value="1"/> </Consumer>
Please remove the AuthenticationToken value from the login request and share the trace file when the problem occurred.
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="LOGIN" streamId="1" containerType="NO_DATA" flags="0x04 (STREAMING)" dataSize="0">
<key flags="0x26 (HAS_NAME|HAS_NAME_TYPE|HAS_ATTRIB)" name=" " nameType="5" attribContainerType="ELEMENT_LIST">
<attrib>
<elementList flags="0x08 (HAS_STANDARD_DATA)">
<elementEntry name="ApplicationId" dataType="ASCII_STRING" data="256"/>
<elementEntry name="ApplicationName" dataType="ASCII_STRING" data="ema"/>
<elementEntry name="Position" dataType="ASCII_STRING" data="192.168.1.115/WIN-Q1OUFFDBGUJ"/>
<elementEntry name="AuthenticationToken" dataType="ASCII_STRING" data="<Remove AuthToken>"/>
<elementEntry name="Role" dataType="UINT" data="0"/>
</elementList>
</attrib>
</key>
<dataBody>
</dataBody>
</REQUEST>0 -
Kindly provide the complete file with the AuthenticationToken removed.
0 -
Thank you for your response.
I provide the contents of the XML.0 -
Thank you for the file.
According to the trace file, the application requested the USD/JPY RIC.
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="5" containerType="NO_DATA" flags="0x46 (HAS_PRIORITY|STREAMING|HAS_QOS)" Qos: Realtime/JustInTimeConflated/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="1" dataSize="0">
<key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="257" name="USD/JPY"/>
<dataBody>
</dataBody>
</REQUEST>I checked and found that this is an invalid RIC.
The correct RIC should be JPY=.
1 -
Thank you for your response.
After correcting the RIC, I was able to retrieve it.
Thank you for your assistance0
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
- 685 Datastream
- 1.4K DSS
- 618 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 655 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛