If you have replaced JAVA_HOME or the absolute path to the java executable and your application does not start, first run the following command to check if all necessary components for Zing, the JDK (ZVM), the Zing System Tools (ZST) and the /etc/zing/license file are installed completely:
If the test with "java -version" works fine, but your application not, then maybe the -Xmx settings for the maximum Java heap size was set too high. Zing supports up to 8 TByte heap size, but is of course practically limited by the free RAM your system provides. Please check the stdout and stderr log files of your application to identify the cause in detail.
Here an example for Tomcat:
# tail /var/log/tomcat8/catalina.out
Error occurred during initialization of VM
Memory management: unable to fund java heap account
Setting -Xmx20G in JAVA_OPTS for Tomcat on this system with 30 GBytes RAM solved the issue.
To identify the maximum value for -Xmx of your system, use the following command:
The value at the column Reservable, line Free shows the maximum possible -Xmx value in MBytes.