EMA ChannelSet failover

Hi
I'm testing NiProvider failover using the <ChannelSet value="Channel_1,Channel_2"/> option.
I've intentionally set Channel_1 to an invalid host to force it to failover immediately when I start my application. This appears to work fine and I get a "Login accepted by host message" from Channel_2. However when I attempt to start publishing data it throws the following exception.
Jan 10, 2018 1:08:41 PM com.thomsonreuters.ema.access.OmmNiProviderImpl submit
SEVERE: loggerMsg
ClientName: NiProvider_1_1
Severity: Error
Text: Internal error: rsslChannel.submit() failed in OmmNiProviderImpl.submit(RefreshMsg)RsslChannel 0
Error Id -1
Internal sysError 0
Error Location Reactor.submitChannel
Error Text ReactorChannel is closed, aborting.
loggerMsgEnd
Channel_2 works fine if I connect directly to it ie if I use <ChannelSet value="Channel_2"/> so I assume there is an issue with the failover mechanism.
anyone having this issue as well ?
thanks
I can see it may be linked to when I request the dictionary from Channel_2 after I receive the login message.
java.lang.NullPointerException
at com.thomsonreuters.ema.access.NiProviderDictionaryItem.rsslSubmit(DictionaryCallbackClient.java:1920)
at com.thomsonreuters.ema.access.NiProviderDictionaryItem.open(DictionaryCallbackClient.java:1777)
at com.thomsonreuters.ema.access.ItemCallbackClient.registerClient(ItemCallbackClient.java:1990)
at com.thomsonreuters.ema.access.OmmBaseImpl.registerClient(OmmBaseImpl.java:385)
at com.thomsonreuters.ema.access.OmmNiProviderImpl.registerClient(OmmNiProviderImpl.java:280)
at com.thomsonreuters.ema.access.OmmNiProviderImpl.registerClient(OmmNiProviderImpl.java:263)
Best Answer
-
I can replicate the same issue with EMA Java 1.1.1's NIProvider example 350 application. If the application does failover to the second ADH, the application encounters the same exception when the API sends Dictionary Request message to the second ADH.
You can submit this issue in GitHub issue page to the Development team directly.
Please see my exception messages below:
Jan 11, 2018 6:13:06 PM com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback
WARNING: loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error initializing channel: errorId=-1 text=Connection refused: no further information
loggerMsgEnd
Jan 11, 2018 6:13:07 PM com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback
INFO: loggerMsg
ClientName: ChannelCallbackClient
Severity: Info
Text: Received ChannelUp event on channel Channel_3
Instance Name Provider_1_1
Component Version adh3.2.0.L1.linux.tis.rrg 64-bit
loggerMsgEnd
Exception in thread "main" java.lang.NullPointerException
at com.thomsonreuters.ema.access.NiProviderDictionaryItem.rsslSubmit(DictionaryCallbackClient.java:1920)
at com.thomsonreuters.ema.access.NiProviderDictionaryItem.open(DictionaryCallbackClient.java:1777)
at com.thomsonreuters.ema.access.ItemCallbackClient.registerClient(ItemCallbackClient.java:1990)
at com.thomsonreuters.ema.access.OmmBaseImpl.registerClient(OmmBaseImpl.java:380)
at com.thomsonreuters.ema.access.OmmNiProviderImpl.registerClient(OmmNiProviderImpl.java:280)
at com.thomsonreuters.ema.access.OmmNiProviderImpl.registerClient(OmmNiProviderImpl.java:263)
at com.thomsonreuters.ema.examples.training.niprovider.series300.example350__Dictionary__Streaming.NiProvider.main(NiProvider.java:135)0
Answers
-
thanks for the confirmation. I will raise this on the github issue list.
As a workaround, if it there is a failover I've loaded the dictionary from file which allows me to continue to publish.
0 -
Hello @david.gardiner
Please be informed that the issue has been fixed in Elektron SDK Java 1.2.0
(EMA Java 3.2.0).
I have tested the issue with Elektron SDK Java 1.2.0, the NIProvider example 350 application can download Dictionary information from the second ADH without any problems when it fail-over to the second ADH.
You can download Elektron SDK Java 1.2.0 from the following links:
- https://developers.thomsonreuters.com/elektron/elektron-sdk-java/downloads
- https://github.com/thomsonreuters/Elektron-SDK
Please see my replication log that works fine with Elektron SDK Java 1.2.0 at log-emaj-120.zip.
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
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 WebSocket API
- 37 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
- 275 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛