I am doing multiple-step installations of TRIRIGA Application Platform on Red Hat Enterprise Linux (RHEL) 7.2 platform. I am installing TRIRIGA 3.4, then 3.4.2, then 188.8.131.52. I have WebSphere Application Server (WAS) ND 184.108.40.206. I have multiple environments. I keep running into little issues.
So far, I have not been able to install TRIRIGA (any version) in one try. The latest error I have received, when installing version 220.127.116.11, is an out-of-memory error. Can anyone tell me how much memory I really need? This is what I have in the error:
[5/16/16 12:12:03:058 EDT] 00000021 SystemErr R java.lang.OutOfMemoryError: Java heap space
[5/16/16 12:12:03:059 EDT] 00000021 SystemErr R at java.io.PrintStream.(PrintStream.java:130)
[5/16/16 12:12:03:059 EDT] 00000021 SystemErr R at java.io.PrintStream.(PrintStream.java:176)java.lang.OutOfMemoryError: Java heap space at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1905)
[5/16/16 12:12:03:059 EDT] 000000bf SystemErr R
[5/16/16 12:12:03:059 EDT] 000000bf SystemErr R Caused by: java.lang.OutOfMemoryError: Java heap space
This is caused by not enough memory being allocated to the WAS install script. There is a memory setting: JVM_EXTRA_CMD_ARGS that is targeted to be added in the next release, reported with APAR IV82864. You can get around this by adding a new line (2nd line) to the was-ant file (Linux/UNIX):
export JVM_EXTRA_CMD_ARGS=”-Xms524m -Xmx4096m”
For Windows, edit was-ant.bat and add a new 2nd line:
set JVM_EXTRA_CMD_ARGS=”-Xms524m -Xmx4096m”
Then, you can run the command:
That will completely set up WAS ND, and not run out of memory.