createOmmConsumer is throwing java exception
I'm making this call
EmaFactory.createOmmConsumer(e.Config.host(hostStr).username(char(username)))
using a valid username, host, and port. I'm connecting to a remote machine (the St. Louis test lab). It was working until this morning. Not sure if the lab is down but anyone know what this exceptoin means:
Java exception occurred: java.lang.AssertionError at com.thomsonreuters.upa.valueadd.domainrep.rdm.dictionary.DictionaryMsgImpl.state(DictionaryMsgImpl.java:264) at com.thomsonreuters.ema.access.ChannelDictionary.processCallback(DictionaryCallbackClient.java:1160) at com.thomsonreuters.ema.access.DictionaryCallbackClient.rdmDictionaryMsgCallback(DictionaryCallbackClient.java:92) at com.thomsonreuters.upa.valueadd.reactor.Reactor.sendDictionaryMsgCallback(Reactor.java:1296) at com.thomsonreuters.upa.valueadd.reactor.Reactor.sendAndHandleDictionaryMsgCallback(Reactor.java:1311) at com.thomsonreuters.upa.valueadd.reactor.WlItemHandler.callbackUser(WlItemHandler.java:2450) at com.thomsonreuters.upa.valueadd.reactor.WlItemHandler.sendStatus(WlItemHandler.java:1476) at com.thomsonreuters.upa.valueadd.reactor.WlItemHandler.requestTimeout(WlItemHandler.java:2879) at com.thomsonreuters.upa.valueadd.reactor.WlStream.timeout(WlStream.java:336) at com.thomsonreuters.upa.valueadd.reactor.Watchlist.timeout(Watchlist.java:314) at com.thomsonreuters.upa.valueadd.reactor.Reactor.processWorkerEvent(Reactor.java:2076) at com.thomsonreuters.upa.valueadd.reactor.Reactor.dispatchChannel(Reactor.java:1393) at com.thomsonreuters.upa.valueadd.reactor.ReactorChannel.dispatch(ReactorChannel.java:410) at com.thomsonreuters.ema.access.OmmConsumerImpl.rsslReactorDispatchLoop(OmmConsumerImpl.java:504) at com.thomsonreuters.ema.access.OmmConsumerImpl.handleAdminReqTimeout(OmmConsumerImpl.java:1187) at com.thomsonreuters.ema.access.OmmConsumerImpl.initialize(OmmConsumerImpl.java:197) at com.thomsonreuters.ema.access.OmmConsumerImpl.<init>(OmmConsumerImpl.java:92) at com.thomsonreuters.ema.access.EmaFactory.createOmmConsumer(EmaFactory.java:158)
Best Answer
-
When EmaFactory.createOmmConsumer(..) is called, EMA sends login, request source directory, and request dictionary to the server.
Based on StackTrace, I suspect that the problem occurred when
EMA requested dictionary e.g. dictionary request timeout (the server did not
send dictionary response within timeout). I simulated dictionary
request timeout and tested with the latest EMA,Elektron-SDK1.0.5(EMA 3.0.2.L1),
but the problem did not occur. I got “State: Open/Suspect/None - text:
"Request timeout"” instead of java.lang.AssertionError. What is
Elekton SDK/EMA version that you use? I think you do not use the latest EMA
because I cannot find com.thomsonreuters.ema.access.OmmConsumerImpl.initialize(..)
and handleAdminReqTimeout(..) in it. Could you test with the latest EMA(Elektron-SDK1.0.5)?
If the problem still occurs with the latest EMA(Elektron-SDK1.0.5), please post
EMA trace log. The log shows messages sent between client/server. You can
enable the log by adding XmlTraceToStdout=1 in
"Channel_1",default channel node, in EmaConfig.xml as shown below:<Name value="Channel_1"/>
<!-- ChannelType possible values are:-->
<!-- ChannelType::RSSL_SOCKET - TCP IP connection type-->
<!-- ChannelType::RSSL_HTTP - Http tunnel connection type-->
<!-- ChannelType::RSSL_ENCRYPTED - Https tunnel connection type-->
<!-- ChannelType::RSSL_RELIABLE_MCAST - Reliable multicast connection type-->
<ChannelType value="ChannelType::RSSL_SOCKET"/>
<!-- CompressionType is optional: defaulted to None-->
<!-- possible values: None, ZLib, LZ4-->
<CompressionType value="CompressionType::None"/>
<GuaranteedOutputBuffers value="5000"/>
<!-- ConnectionPingTimeout is optional: defaulted to 30000-->
<ConnectionPingTimeout value="30000"/>
<!-- TcpNodelay is optional: defaulted to 1 -->
<!-- possible values: 1 (tcp_nodelay option set), 0 (tcp_nodelay not set)-->
<TcpNodelay value="1"/>
<Host value="localhost"/>
<Port value="14002"/>
<XmlTraceToStdout value="1"/>
</Channel>Please put EmaConfig.xml in application run directory.
0
Answers
-
If you require any help regarding this question, please let me know.
0 -
Thanks Pimchaya. All set on this one.
0 -
Check this one to know more about...Exceptions in Java
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 中文论坛