Migrating legacy SFC (RTMDS v3) Java client to EMA

Hi all,
I’m moving an ancient Java app from the SFC API to EMA Java. The local RTMDS v3 host listens on 8101, 14002, and 24002. I was told I can reuse the same DACS user with EMA.
Connecting EMA to 8101 gives:
ChannelDownReconnecting ... Error initializing channel
Connecting EMA to 14002 or 24002 results in connection refused.
What might be the problem? Which port should EMA use in this setup?
(Example trace, user masked)
19:58:13.486 [main] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: LoginCallbackClient
Severity: Trace
Text: RDMLogin request message was populated with this info:
LoginRequest:
streamId: 1
userName: ********************
streaming: true
nameType: 1
applicationId: 256
applicationName: ema
position: 192.168.68.105/97VC9K3
19:58:13.692 [main] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Attempt to connect using
1] SOCKET
Channel name Channel_APAC_1
Instance Name Consumer_APAC_1_1
RsslReactor @67427b69
InterfaceName
hostName 146.242.129.225
port 8101
CompressionType None
tcpNodelay true
reconnectAttemptLimit -1
reconnectMinDelay 1000 msec
reconnectMaxDelay 5000 msec
guaranteedOutputBuffers 5000
numInputBuffers 10
sysRecvBufSize 65535
sysSendBufSize 65535
connectionPingTimeout 30000 msec
initializationTimeout 5 sec
19:58:13.822 [main] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Received ChannelOpened on channel Channel_APAC_1
Instance Name Consumer_APAC_1_1
19:58:13.824 [main] TRACE com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Trace
Text: Successfully created a Reactor and Channel(s)
Channel name(s) Channel_APAC_1
Instance Name Consumer_APAC_1_1
19:58:14.204 [main] WARN com.refinitiv.ema.access.OmmConsumerImpl - loggerMsg
ClientName: ChannelCallbackClient
Severity: Warning
Text: Received ChannelDownReconnecting event on channel Channel_APAC_1
RsslReactor @67427b69
RsslChannel @49a64d82
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Error initializing channel: errorId=-1 text=Error occurred during connection process.
Answers
-
Hello @dgoloughlin
The EMA API can connect to the OMM Provider (RTDS, ADS, etc) via the RSSL connection (default port is 14002) only. It cannot connect to the SSL connection (port 8101).
Did your server enable RSSL connection yet?
According to this log, it shows that you have set the API to connect to the server via port 8101
Text: Attempt to connect using
1] SOCKET
Channel name Channel_APAC_1
Instance Name Consumer_APAC_1_1
RsslReactor @67427b69
InterfaceName
hostName 146.242.129.225
port 8101Could you please share a snippet code and your EmaConfig.xml 's Consumer and Channel configurations?
Please also give use more detail about your application:
- EMA Java version
- Java version
- OS
- What is the server?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 707 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 15 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 7 Trading API
- 3K Elektron
- 1.5K EMA
- 260 ETA
- 571 WebSocket API
- 41 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.2K Refinitiv Data Platform
- 17 CFS Bulk File/TM3
- 907 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 197 TREP Infrastructure
- 232 TRKD
- 921 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 106 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛