We are using cloverETL 188.8.131.52/9, and we hit the following issue in our production servers:https://bug.javlin.eu/browse/CLO-5651
We tried to disable Direct Memory, by putting "USE_DIRECT_MEMORY = false" into a new file in tomcat_dir/conf/engine.config
Then adding a line to our clover config:
After restarting the server, we see confirmation that direct memory is off in the Configuration / CloverETL info / Engine Properties section (see first attachment)
but when we go to the monitoring section, we still see the server using direct memory (see second attachment)
Are we missing any steps? or is that second screen shot in the monitoring section showing something unrelated that just happen to be labeled Direct Memory, and direct memory is truly now off?
Please let us know, as we don't know if the setting took place.