How to fix EmaConfig.xml parsing failure and connection fallback in RTSDK Java?

Question

I'm reaching out because we've gotten a bit stuck trying to connect to the RTDMS environment using the Java SDK (specifically running the runConsumer100 example). We are setting everything up on a Debian server and something strange is happening: the SDK completely ignores our EmaConfig.xml file and keeps falling back to localhost:14002 by default. Our goal is to point to the IP xxxxxxxxxxx (using the parameters -u 'EM3 MFSA ES05938' -s HEDD), but we keep running into these two errors in our server logs: * The validator rejects the classic structure and requires us to use . * When we switch it to groups, we hit a [Fatal Error] EmaConfig.xml:1:7: A pseudo attribute name is expected.. Since we are on a Linux/Debian environment, we suspect this might be a weird encoding issue, line endings, or some invisible character introduced when processing the XML on this system. Either way, this error causes the parser to discard the physical file entirely.

wasin.w V3 · Answer

Hello @Alex_Interacso

By default, the EMA API looks for the EmaConfig.xml file in the same location as an application. If you store the EmaConfig.xml file in other location, you can see the ex111_MP_UserSpecifiedFileCfg example about how to parse the EmaConfig.xml file path to the API.

Please run the EMA API on the supported Java SDK versions as well. You can check on the API Compatibility Matrix document link given by my colleague.

Jirapongse · Answer

@Alex_Interacso

Thank you for reaching out to us.

According to the API Compatibility Matrix, the SDK doesn't support Debian. Please run the SDK on the supported platforms.

The ex100_MP_Streaming example sets the localhost:14002 in the code which will override the value set in the configuration file. You may need to remove the host method calling in the code.

If this doesn't solve the problem, please share the code and EmaConfig.xml file.

EXPLORE OUR SITES