Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Java memory tuning override during upgrades
-
The Java Memory Tuning instructions in the Wiki are overwritten during upgrades because Mango upgrades overwrite /bin/ma-start.sh. What is the recommended persistent method for increasing Java memory? Could this be causing startup issues or other errors that don't necessarily present as outOfMemory errors?
-
This section of the wiki explaines it:
http://infiniteautomation.com/wiki/doku.php?id=system_admin:javamemorytuning#tuning_mangoTuning Mango
To make the tuning relatively easy, Mango comes packaged with extension scripts. These are located in MA_HOME/bin/ext-available and include redirecting output, enabling the debugger, controlling the garbage collector, and tuning the memory boundaries. These scripts work by setting variables which will be passed to the JVM when Java is launched, just as is done in the other method below. To use these scripts, either move them into MA_HOME/bin/ext-enabled or create a symlink from MA_HOME/bin/ext-enabled to the script in ext-available.
-
Right, but per my post, won't those customizations be lost during upgrades?
-
No, the ext-enabled folder is empty by default so anything you put in there will persist across upgrades.
-
Thanks, that's a great improvement.
-
Yes it's very handy. I also just updated the wiki to clarify it. Thanks.
-
Thanks for clarifying this in the Wiki. Since /bin/ext-enabled is not under /overrides, it is not obvious that it would survive upgrades.
