Getting -> Error text Error initializing channel: errorId=-1 text=Error occurred during connection p
Best Answer
-
The error
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(Unknown Source)
at java.util.ArrayList.get(Unknown Source)that you encounter is similar to the problem in this How to connect to TREP using EMA topic. The problem occurs when you connect the EMA API to the ADS older versions that does not provide component version to the API. After EMA connects to older version of TREP, it tries to get TREP component version. If it fails, the exception is thrown.
What is the ADS version that you are using?
If your ADS version is 2.2 or older, they are already end of life and no longer supported, I suggest you upgrade to ADS 3.0 which is a latest version.
0
Answers
-
I can replicate the same message by using a telnet connects to the EMA Java Interactive Provider example 100 (IProvider.java), and then quit a telnet command. The example shows the same log messages
SEVERE: loggerMsg
ClientName: ServerChannelHandler
Severity: Warning
Text: Received ChannelDown event on client handle 1
Instance Name Provider_1_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error initializing channel: errorId=-1 text=Error occurred during connection process.
loggerMsgEndBased on the above log message, the problem seems to happen when the provider application receives a connection from consumer client. What is the consumer application that you are using? Can you re-test by using the EMA Java Consumer example 100 as a consumer client to verify the problem?
0 -
Hi @Wasin Waeosri
I have used the below examplecom.thomsonreuters.ema.examples.training.consumer.series100.example100__MarketPrice__Streaming.Consumer.java class (client) to connect to Reuters servers and get the Market pricing data
But I got as below
For server 1:Error text Error initializing channel: errorId=-1 text=Error occurred during connection process
For server 2:Error text Error initializing channel: errorId=-1 text=Handshake failed with far end. No more Protocols to try
Please guide me
0 -
Hi @Wasin Waeosri
I have used the below examplecom.thomsonreuters.ema.examples.training.consumer.series100.example100__MarketPrice__Streaming.Consumer.java class (client) to connect to Reuters servers and get the Market pricing data
But I got as below
For server 1:Error text Error initializing channel: errorId=-1 text=Error occurred during connection process
For server 2:
Error text Error initializing channel: errorId=-1 text=Handshake failed with far end. No more Protocols to try
Please guide me
0 -
I can replicate the both messages when setting the Consumer example connects to the SSL publisher which is unsupported by the EMA Java. The EMA Java supports the RSSL connection only, I suggest you configure the host to the RSSL port as following example
consumer = EmaFactory.createOmmConsumer(config.host("<ADS IP>:<RSSL Port>").username("user"));
If the problem still persists after you changed the port to the RSSL port, please give us the server details (server IP, Port, snippet of code that set the connection).
0 -
Hi @Wasin Waeosri,
I have used the following code for conectionconsumer = EmaFactory.createOmmConsumer(config.host("stprtrsp2p:8101").username("721002"));
orconsumer = EmaFactory.createOmmConsumer(config.host
("rcortrsp2p:8101").username("721002"));
Server detals:stprtrsp2p
rcortrsp2p
Port details:
8101Username
721002
Please help me.
0 -
Port 8101 is for legacy SSL connection. As Wasin mentioned, EMA only uses RSSL connection, which should be port 14002. Have you tried it yet?
0 -
Hi @Steven Peng and @Wasin Waeosri,
I tried with RSSL port 14002 as below:consumer = EmaFactory.createOmmConsumer(config.host("rcortrsp2p:14002").username("user"));
But I got an exception like this
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(Unknown Source)
at java.util.ArrayList.get(Unknown Source)
at com.thomsonreuters.ema.access.ChannelCallbackClient.reactorChannelEventCallback(ChannelCallbackClient.java:366)
0 -
Hello @Chaitanya.Vishnubhotla,
Please verify the details of your connection:
- host
- port
- username
with your market data team.
EMA does not support SSL protocol, it communicates to the market data infrastructure over more efficient, new RSSL protocol.
However port 8101, is a default SSL port. RSSL infra port is defaulted to 14002. But it can be a different port, your market data team will be able to confirm your correct connection details.
0 -
Is your server DACS enabled?
You need to specify a valid DACS user ID in the username() parameter:
consumer = EmaFactory.createOmmConsumer(config.host("rcortrsp2p:14002").username("user"));
Also, do you know the version of your server? I believe
ChannelCallbackClient.java: line 366 is the place where reactorChannelEventCallback display the ADS version information but example 100 is a very simple code and I've never heard anyone has problem with it. If you still have problem, please display the main() method here so we can take a look.
0 -
Hi @Wasin Waeosri
Thanks for advice. I reached the MDS team and got the updated servers versions and now I am able to connect to servers.
0 -
Hi @steven.peng
Thanks for advice. I reached the MDS team and got the updated servers versions and now I am able to connect to servers.
0 -
Hi,
I receive the below error trying to run example100. Could you please help me?
SEVERE com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback loggerMsg ClientName: ChannelCallbackClient Severity: Error Text: Received ChannelDown event on channel Channel Instance Name EmaConsumer_1 RsslReactor Channel is null Error Id 0 Internal sysError 0 Error Location Reactor.processWorkerEvent Error text Error initializing channel: errorId=-1 text=Error occurred during connection process. loggerMsgEnd login failed (timed out after waiting 45000 milliseconds) for ......)
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 中文论坛