Running the TRIRIGA install script in order to upgrade (e.g. from 220.127.116.11 to 3.5) when WebSphere is the application server, can fail in some cases with an Out of Memory error when set-soap-timeout is run. This problem can happen even though sufficient memory (e.g. 4 GB) was specified in the install/upgrade script and written to the TRIRIGA build.properties file.
It would seem that before launching the ws_admin.sh script, the TRIRIGA install scripts need to run something like ‘export JVM_EXTRA_CMD_ARGS=”-Xms1G -Xmx2G”‘ in order to set the Java heap size correctly. Without this, the Java heap used by the install scripts seem to start with a 512 MB heap size.
WebSphere’s script ws_ant default values were too small. We resolved an issue with the installation of traditional WebSphere, where the default heap size of the ws_ant shell script was too small. The JVM_EXTRA_CMD_ARGS needed to be set to a higher number.