EMA Java Warning "Login stream was closed." with "RDMDictionary stream was closed with status messag

tonyzhuTR

One of our TREP3.2 client who uses EMA Java to access TREP and logged following warning msgs.

Can we know what it means and associated impact? How to resolve it, thanks.

2020-05-18 11:22:44.263|WARN|c.t.e.a.OmmConsumerImpl||loggerMsg

ClientName: ChannelDictionary

Severity: Warning

Text: RDMDictionary stream was closed with status message

streamId 4

Reason State: Closed/Suspect/None - text: "Login stream was closed."

loggerMsgEnd

2020-05-18 11:22:44.362|WARN|c.t.e.a.OmmConsumerImpl||loggerMsg

ClientName: ChannelDictionary

Severity: Warning

Text: RDMDictionary stream was closed with status message

streamId 3

Reason State: Closed/Suspect/None - text: "Login stream was closed."

loggerMsgEnd

2020-05-18 11:22:44.362|WARN|c.t.e.a.OmmConsumerImpl||loggerMsg

ClientName: ChannelDictionary

Severity: Warning

Text: RDMDictionary stream was closed with status message

streamId 4

Reason State: Closed/Suspect/None - text: "Login stream was closed."

loggerMsgEnd

umer.nalla

Hi @tony.zhu

If the Login stream is closed, that means you are not logged into the server, so you cannot download the data dictionary, nor can you make subscription request or snapshots.

Are they using their own code or one of our examples?

If they are using their own code, can they try one of our examples instead and see what happens?

You said it happens on startup - every time or just occasionally?

If it happens everytime: Have they checked their credentials - dacs user name? Are they using the correct Hostname / ports?

If they are using EMAConfig.xml - does it work when they hardcode the host and port etc into the Java code? If it works with hardcoded values, then this means the API cannot find the EMAConfig.xml file.

Please provide answers to all questions so we can assist fully.

umer.nalla

Hi @tony.zhu

You will need to provide additional information so we can assist

When does this happen? All the time or occasionally? At startup of the application or whilst it has been running fine for a while?

Are they using one of our examples EMA Java examples or their own code?

If they are using their own code, does the problem also occur if they use one of our EMA Java examples instead?

There are some existing posts on this error message which may also help

https://community.developers.refinitiv.com/questions/21086/data-streaming-auto-logout-login-stream-was-closed.html

https://community.developers.refinitiv.com/questions/49217/receive-error-message-of-login-stream-was-closed.html

tonyzhuTR

Hi @Umer Nalla

Above logs happened at startup. Can we know what's the meaning of "RDMDictionary stream was closed with status message"?

How does it affect the subsequent subscription or snapshot request?Thanks.

tonyzhuTR

@Umer Nalla,

Thanks for your detailed clarification. After putting RDMD files in the working dir as client's consuming App, such issue doesn't happen by far.

umer.nalla

Hi @tony.zhu

If by RDMD files you mean the dictionary files - I would not recommend using local dictionary files. The dictionary changes several times a year - as and when fields are added/deleted/modified.

This means that there is a possibility of the application crashing if it using an outdated dictionary and cannot parse a new field - therefore the use of ChannelDictionary is strongly recommended - unless a FileDictionary is essential (e.g. use of custom FIds)