nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to resolve connection error on upgrading jar version?

RiskFactors

We upgraded the jar version from 'com.thomsonreuters.ema:ema:3.3.0.1' to 'com.refinitiv.ema:ema:3.8.3.0'. We are using the OmmConsumerClient interface to establish a connection to our on prem Reuters servers. We are using the EMAConfig.xml route to connect to the servers.

Upon upgrading the jar version we are getting below error, can you please advise on what if any changes to the api is required? We were able to use the same config with the older jar version and able to connect without any errors.

May 05 01:12:02 ERROR [main] c.r.ema.access.OmmConsumerImpl:748 loggerMsg
ClientName: ChannelCallbackClient
Severity: Error
Text: Received ChannelDown event on channel Channel_3
Instance Name Consumer_1_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Reconnection failed: port out of range:-1
loggerMsgEnd

May 05 01:12:05 ERROR [main] c.r.ema.access.OmmConsumerImpl:1884 loggerMsg
ClientName: Consumer_1_1
Severity: Error
Text: login failed (timed out after waiting 45000 milliseconds) for <server name>:)
loggerMsgEnd

Find more posts tagged with

java

connection

#technology

Accepted answers

All comments

Jirapongse

@RiskFactors

Thank you for reaching out to us.

It shows this error.

Error text Reconnection failed: port out of range:-1

I am not sure why it shows "-1". Typically, it looks like this:

login failed (timed out after waiting 45000 milliseconds) for 127.0.0.1:14002)

The default port is 14002. Please check the port configuration.

You may try the ex100_MP_Streaming example in the package.

RiskFactors

we have a log like what you are suggesting,

'login failed (timed out after waiting 45000 milliseconds) for <host name>:)'

We didn't exclusively put in the port in the xml config, is that mandatory with the new jar version?

RiskFactors

We are using the TrepsClient object with a dacsId to establish connection and have the EmaConfig.xml for the config files, where we have our consumer and channel setup.

Jirapongse

Yes, you need to specify the Port configuration in the Channel.

		<Channel>
			<Name value="Channel_1"/>
			<ChannelType value="ChannelType::RSSL_SOCKET"/>
			<CompressionType value="CompressionType::None"/>
			<GuaranteedOutputBuffers value="5000"/>
			<InitializationTimeout value="30000"/>
			<ConnectionPingTimeout value="30000"/>
			<TcpNodelay value="1"/>
			<Host value="192.168.42.195"/>
			<Port value="14002"/>
		</Channel>

RiskFactors

Even with the port, getting the above same error.

Jirapongse

@RiskFactors

Did you see to port number in the error text?

'login failed (timed out after waiting 45000 milliseconds) for <host name>:<port>)'

If not, we may set it in the wrong place.

You may enable the EMA trace log by referring to the Learn how to direct EMA Java log to Java Logging API article. Please share the trace log.

RiskFactors

May 08 01:37:49 ERROR [main] c.r.ema.access.OmmConsumerImpl:748 loggerMsg
ClientName: ChannelCallbackClient
Severity: Error
Text: Received ChannelDown event on channel Channel_3
Instance Name Consumer_1_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Reconnection failed: port out of range:-1
loggerMsgEnd

May 08 01:37:52 ERROR [main] c.r.ema.access.OmmConsumerImpl:1884 loggerMsg
ClientName: Consumer_1_1
Severity: Error
Text: login failed (timed out after waiting 45000 milliseconds) for wppra96a0325.wellsfargo.com:)
loggerMsgEndMay 08 01:37:49 ERROR [main] c.r.ema.access.OmmConsumerImpl:748 loggerMsg
ClientName: ChannelCallbackClient
Severity: Error
Text: Received ChannelDown event on channel Channel_3
Instance Name Consumer_1_1
RsslReactor Channel is null
Error Id 0
Internal sysError 0
Error Location Reactor.processWorkerEvent
Error text Reconnection failed: port out of range:-1
loggerMsgEnd

We are not seeing the port, just the hostname is coming up, also one more note, the host name that is coming up in the log is not even in the list of channels we have mentioned, not sure how and where it is trying to connect to.

wasin.w V3

Hello @RiskFactors

The EmaConfig.xml file should be in the same location as an application (unless you specify the file location to the EmaFactory.createOmmConsumerConfig(configFile) statement, see ex111_MP_UserSpecifiedFileCfg example).

Is there another EmaConfig.xml file being used by an application that wasn't configured properly?
Does the code use the EmaConfig.xml or populate ADS host and port from your internal system/config, then put to the EMA via the code?

RiskFactors

We have a single EMAConfig.xml file that has all the server names under the channel list. We keep this xml file in our classpath as per earlier recommendation.

There was no upgrade to the config, nor to the code, just the dependency was upgrade as stated above and corresponding package name update to access required classes.

Jirapongse

It seems that the Port configuration is not loaded properly or the application may load the different EMAConfig.xml. file.

Please enable the EMA trace log by referring to the Learn how to direct EMA Java log to Java Logging API article.

handlers=java.util.logging.ConsoleHandler, java.util.logging.FileHandler

.level=FINEST

java.util.logging.ConsoleHandler.level=FINEST

java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter


java.util.logging.FileHandler.level=FINEST

java.util.logging.FileHandler.pattern= %h/java%u.log

java.util.logging.FileHandler.limit=50000000

java.util.logging.FileHandler.count=20

java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter

java.util.logging.SimpleFormatter.format=%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS.%1$tL %4$-7s %2$s %n%5$s

Please share the trace log and your configuration file.

unknown

This content has been removed.

RiskFactors



<EmaConfig>

    <ConsumerGroup>

        <ConsumerList>

            <Consumer>

                <Name value="Consumer_1"/>

                <!-- ChannelSet specifies an ordered list of Channels to which OmmConsumer will attempt -->

                <!-- to connect, one at a time, if the previous one fails to connect -->

                <ChannelSet value="Channel_1, Channel_2, Channel_3, Channel_4"/>

                <ReconnectAttemptLimit value="10"/>

                <XmlTraceToStdout value="0"/>

            </Consumer>

        </ConsumerList>

    </ConsumerGroup>

    <ChannelGroup>

    <ChannelList>

        <Channel>

            <Name value="Channel_1"/>

            <Host value="<host-name>"/>

			<Port value="14002"/>

        </Channel>

        <Channel>

            <Name value="Channel_2"/>

            <Host value="<host-name>"/>

			<Port value="14002"/>

        </Channel>

        <Channel>

            <Name value="Channel_3"/>

            <Host value="<host-name>"/>

			<Port value="14002"/>

        </Channel>

        <Channel>

            <Name value="Channel_4"/>

            <Host value="<host-name>"/>

			<Port value="14002"/>

        </Channel>

    </ChannelList>

    </ChannelGroup>

</EmaConfig>

EMAConfig.xml file

Jirapongse

Typically, it loads the configuration file from the working directly. To change the location of the file, please check this ex111_MP_UserSpecifiedFileCfg example.

I need the log at the FINEST level.

handlers=java.util.logging.ConsoleHandler, java.util.logging.FileHandler

.level=FINEST



java.util.logging.ConsoleHandler.level=FINEST


java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter



java.util.logging.FileHandler.level=FINEST

java.util.logging.FileHandler.pattern= %h/java%u.log


java.util.logging.FileHandler.limit=50000000


java.util.logging.FileHandler.count=20


java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter

Please check the Learn how to direct EMA Java log to Java Logging API article regarding how to enable the EMA logging.

The message indicates that the application is trying to close the batch stream.

    Text:    Invalid attempt to close batch stream. Instance name='Consumer_1_6'.

The Batch handle is automatically closed by EMA once it makes the batch request - as each item has its own individual handle & stream established by the API - since each item is updated individually and therefore needs its own stream.

If you want to close the individual items you can extract the handle from the event that you receive in your event handlers. For example:

	public void onRefreshMsg(RefreshMsg refreshMsg, OmmConsumerEvent event)

	{

		System.out.println(event.handle());

		System.out.println(refreshMsg);

	}

RiskFactors

The example with the config file path setup worked.

On the other error, we were explicitly using the registrationId when we are registering a client(consumer.registerClient()) and explicitly unregistering it, using consumer.unregister(registrationId). Are you implying we don't need to unregister these consumer streams explicitly?

Jirapongse

@RiskFactors

If you uses a batch request, you need to get the items' handles from the callback method and use items' handles with the consumer.unregister method.

You should not call the consumer.unregister method with the batch handle.

RiskFactors

According to the example you provided, do we not need to uninitialize the consumer as well?

wasin.w V3

Hello @RiskFactors

When an application sends a batch items request to the Real-Time server, the first thing we get back is a Status message confirmation of the Batch request:

Item Name: <not set>

Service Name: ELEKTRON_DD

Item State: Closed / Ok / None / 'Stream closed for batch'

This Status message means the server accepts a batch items request, and that it is now closing that batch request stream. This is because the server is going to create individual streams for each of the RICs and allocate a unique ID to each stream. An application can get these unique streams handle via the onRefreshMsg() callback method as mentioned by my colleague.

Regarding uninitialized the OmmConsumer object, it should be used when you need to stop the EMA API process and disconnect from the server only.

Jirapongse

The example calls the consumer.uninitialize.

The consumer.uninitialize method also closes all handles, so the application does not need to unregister each handle individually.

EXPLORE OUR SITES