iManager is failing with server java.lang.OutOfMemoryError

This problem will be fixed in a future support pack for Novell NetWare 6.5

Workaround:

1. Create a new start up ncf file for Tomcat SYS:SYSTEM/TC4START.NCF file containing the following load command:

#BEGIN TC4START.NCF

java -vm100m -Xmx540m -envCWD=sys:/tomcat/4 -Djavax.net.ssl.trustStore=sys:/adminsrv/conf/.keystore -Dsun.io.useCanonCaches=false -classpath sys:/tomcat/4/bin/bootstrap.jar;sys:/java/lib/jclient.jar -Dcatalina.base=sys:/tomcat/4 -Dcatalina.home=sys:/tomcat/4 -Djava.io.tmpdir=sys:/tomcat/4/temp org.apache.catalina.startup.Bootstrap start

#END TC4START.NCF

2. Change load command in AUTOEXEC.NCF for Tomcat executing"TC4START.NCF" instead "Tomcat4.ncf".
4. Restart Tomcat with executing TC4STOP.NCF and new TC4START.NCF or Reset Server

Than you can look for the best settings by changing -vm & -Xmx in this TC4START.NCF file fo tuning.

Novell discovered that the -vm & -Xmx are not passed on to Tomcat.
The values are changed in the CATALINA_OPTS variable but Tomcat ends up being started without those changed values & instead Tomcat uses the default values.

In other words, there is a problem between the Tomcat4.ncf, Startup.ncf & Catalina.pl files.

You can easily verify which values of -vm & -XMX are being used by doing the following:
1. Start Tomcat with the new NCF file described above.
2. Issue the following command at the server console to get Tomcat's ID:
java -show
3. Issue the following command at the server console to see the command that was used to start the Tomcat (this should be the content of the new NCF file):
java -showapp (no space between -showapp and Tomcat's ID)
4. Issue the following command at the server console:
java -showmemory
5. Look at the "Reserved Heap" and the "Reserved Virtual Memory Pool" sections to verify that they match what the customer has set the sizes to.