Hello @valeriu.neacsu

I can replicate the same message with EMA Java 1.2.1 example 100 - Consumer.java by setting the application to connect to an invalid port.

Example code:

consumer  = EmaFactory.createOmmConsumer(config.host("172.20.33.11:8101").username("user")); //8101 is the SSL port, not RSSL port

Example message:

Nov 06, 2018 5:21:26 PM com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback
SEVERE: loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Error
    Text:    Received ChannelDown event on channel Channel_1
	Instance Name Consumer_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.
loggerMsgEnd

login failed (timed out after waiting 45000 milliseconds) for 172.20.33.11:8101)

Please check if you set a valid TREP/OMM Provider RSSL port or not, the default value of the RSSL port is 14002. You can set the RSSL connection via the following EMA statement:

consumer  = EmaFactory.createOmmConsumer(config.host("<TREP/OMM Provider IP>:<RSSL Port>").username("<username>"));

Hello @valeriu.neacsu

Could you please give me more detail on this issue?

1. The EMA Java version that encounters the problem
2. Which example 100 that encounters the problem? (IProvider.java or Consumer.java or NiProvider.java)
3. Snippet of your example source code
4. Replication steps
5. The EmaConfig.xml file

Hi Wasin,

Problem solved, was from port id. I used an SSL port instead RSSL 14002.

Many thanks,

Valeriu

After successfully working on a client for a few weeks now - a client based on consumer113, I am now having trouble connecting and maintaining a connection for more than 15 minutes. This with consumer 113.. (not my client). Sometimes connection is successful, sometimes it tries 5 times and fails. Consumer connection is to us-east-2a us-east-2b. Nothing has changed in the examples since I downloaded the SDK a few weeks ago.. Am using version 3.7.3.0. In contrast, my dinky websocket-based python client runs for a week at a time, though with UAT credentials. Websocket connection is to wss://us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net:443/