Switched to using EmaConfig.xml to handle multiple hosts fallback, but it led to slower processing.

sagnik_haldar · 2025-03-27T05:10:06+00:00

There was an error rendering this rich post.

Earlier we used to point to a single host using the config.host() api in the EmaFactory.createOmmConsumer. But recently we planned to use the EmaConfig.xml file to handle auto fallback using multiple hosts. But that has significantly increased our processing time.

We are seeing a lot new xml logs, which weren't there earlier when we weren't using EmaConfig.xml. Our EmaConfig.xml is setup to have a single consumer and it has multiple channels and in the application we are registering the consumer with the consumer we are creating.

Any ideas why it might be so slow?

Find more posts tagged with

#technology

Accepted answers

Jirapongse

It looks like to be a trace file.

You can disable it.

All comments

Jirapongse

@sagnik_haldar

Thank you for reaching out to us.

Please provide more information regarding this issue.

What version of EMA are you using?
What do you mean by a lot of new xml logs? Can you share their content?
Please share the EmaConfig.xml file that you are using.
How do you determine that the application is slower when using the configuration file?

sagnik_haldar

1. ema version is 3.3.0.1

2. xml tags that can be seen are <seriesEntry>, <elementlist>, <arrayentry>, <array> with a lots more data

3. EmaConfig.xml file is setup similar to 3.4.9 example from emaj config guide pdf. We just omitted port and channel type, letting it use the default values.

4. we are determining slowness in terms of completion time of the process. Where using the same host without the xml config we are done in a minute, whereas with the xml config on average it takes us 4 minutes to complete.

Jirapongse

It looks like to be a trace file.

You can disable it.

sagnik_haldar

Yes, it was related to the XmlTraceToStdout. Too much logging to console was slowing down the overall process. Thanks for the help.

EXPLORE OUR SITES