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,

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.

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)