IV82864: TRIRIGA upgrade script when using WebSphere is failing


Running the TRIRIGA install script in order to upgrade (e.g. from 3.4.2.2 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.

Continue reading

One thought on “IV82864: TRIRIGA upgrade script when using WebSphere is failing

  1. Pingback: Getting an out of memory error when installing 3.4.2.3 on RHEL 7.2 | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s