Memory options for EnsLib.JavaGateway.Service
Is there a best practice to set the memory options (classic xms and xmx) on the JavaGw service in the production?
What can be recommended?
Like specifying 1024M for xmx is for a single process? that process can't grow beyond that value right? what happen if the process reach the memory limit?
Thanks
Pietro
Comments
A common Java error is produced by Java Heap Space, you can find here the most common errors of memory produced by Java:
What can be recommended?
Fixing memory leaks if you see your running jvm process consuming more and more memory.
At the Java Gateway Service, I have specified the following JVM Args
-d64 -XX:+DisableExplicitGC -XX:+AggressiveOptsAt the %JDBCServer level, I have specififed
-d64 -Xmx1024m -XX:+DisableExplicitGC -Xss512kI have often asked for Best Practices but have not had much response. You have to play with the settings as you go...