Hi @Laarni Evelyn Acierto.Santiago

Unfortunately, the information you have provided is very limited - and does not give much to go on.Can you please provide more information so we can help?

The warning you mention does not sound like an EMA warning - do you have any EMA generated output warning/log file?
Is this a new application you are developing?
Or is it an existing app that was working and now does not work?
Is it happening every time you request a dictionary or only intermittently?
What are you connecting to - a TREP server or ERT in Cloud server?

Please see sample error message. I can't upload the whole file.

Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:32:16 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:32:16 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:32:48 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:32:48 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:32:48 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 40. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:33:12 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 40. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:33:12 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 40. <END> -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:33:48 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:33:53 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 32. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:33:53 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 32. <END> -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:34:12 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 40. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:34:21 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:34:21 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. <END> -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:35:14 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 44. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:35:14 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 44. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:35:17 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:35:24 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 32. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:35:51 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 37. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 10:36:14 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 44. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:33:51 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:33:51 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:34:52 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:53:46 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:53:46 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 11:54:46 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 33. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer -- <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:47:47 2019> RSSL login request from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 49. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:47:47 2019> RSSL login accepted for "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 49. <END> <trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:48:47 2019> RSSL disconnect from "LO1_03_RHB_EO10704" at position "172.18.3.23/rate-connector-elektron1.tw.ee" on host "rate-connector-elektron1.tw.ee" using application "256" on channel 49. Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer

Hi @Laarni Evelyn Acierto.Santiago

thanks for the log output.

Can you also answer the other questions I asked - in my post - so we can try and put these disconnects into context?

Hi @Umer Nalla,

Thanks fro response will try to answer.

"The warning you mention does not sound like an EMA warning - do you have any EMA generated output warning/log file?"

- ERROR - loggerMsg ClientName: Consumer_1_1 Severity: Error Text: dictionary retrieval failed (timed out after waiting 45000 milliseconds) for ipadress:port)

app logs:

Caused by: com.thomsonreuters.ema.access.OmmInvalidUsageExceptionImpl: dictionary retrieval failed (timed out after waiting 45000 milliseconds) for ipadress:port) at com.thomsonreuters.ema.access.OmmBaseImpl.ommIUExcept(OmmBaseImpl.java:1317)

"Is this a new application you are developing? Or is it an existing app that was working and now does not work?"

- This is already working application. At some point fetching stopped. Application was restarted and this error appeared and app could not start fetching.

"Is it happening every time you request a dictionary or only intermittently?"

- This was happening always for almost a day.

"What are you connecting to - a TREP server or ERT in Cloud server?"

- Think that TREP but not sure 100% sure, but we are connected to static ip through a vpn.

A bit more logs:

<trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:47:47 2019>

RSSL login request from "*" at position "*" on host "*" using application "256" on channel 49.

<END>

<trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:47:47 2019>

RSSL login accepted for "*" at position "*" on host "*" using application "256" on channel 49.

<END>

<trhlo1slsp03a03.1.ads: Info: Tue Sep 03 13:48:47 2019>

RSSL disconnect from "*" at position "*" on host "*" using application "256" on channel 49.

Reason: rsslRead() failed with code -1 and system error 0. Text: <Impl/ripcsrvr.c:6823> Error:1002 ripcRead() failure. Connection reset by peer

On client side 13:47:48 we get dictionary timeout event

com.thomsonreuters.ema.access.OmmInvalidUsageExceptionImpl: dictionary retrieval failed (timed out after waiting 45000 milliseconds) for ipaddress:port

The client was accepted already after or just before timeout, but I suppose right after and then connection was closed.

Hi @ivan.parker

Thanks for providing the additional information which helps add context to the problem you are experiencing.

You have stated that this application was working fine and then stopped working. 'This was happening always for almost a day.' I understand from the account team that the issue was eventually resolved later in the day - is that correct?

Looking at the log output you included, I can see that you send a login request, the server accepts the login request - but then a minute later the server disconnects you. The data dictionary download failure would be as a result of the server disconnecting you.

I understand from the account team that this issue is being investigated by the server support team and hopefully they will be able to identify the cause of the server disconnect.

This forum is best suited for technical development related issues. Therefore, if the server support team do come back and suggest the problem potentially lies with your application, then feel free to share any information they provide here - if you need help with fixing your application.

@Umer Nalla

"...the issue was eventually resolved later in the day" - yes this is correct

Thanks

HI @Umer Nalla Can we do a tracing into client's EMA?

Hi @Laarni Evelyn Acierto.Santiago

The low-level trace outputs incoming and outgoing messages between the API and the server. I am not entirely sure if this would will help diagnose the issue - as the disconnect is done by the server - but maybe worth a try in case something useful is logged.

Also, enabling low-level trace for extended periods is generally only recommended in a dev/QA environment as it can affect application performance to a considerable degree.

If they can reproduce the problem at will / frequently - then they could enable it in production just for a short period - in order to capture the trace during a disconnect scenario.

Please see this post for details on how to enable Trace if you decide to proceed.