Novell NETWARE 6-DOCUMENTATION Manual page 29

When creating new rbsRole objects in iManage, the tasks for that role should
be assigned from the same rbsCollection container that the role was created in.
Out-of-Memory Errors
If you receive out-of-memory errors when running iManage (Error: 500 on
client browsers and OutOfMemory Java exception on the Server Login
Screen), edit the SYS:TOMCAT\33\BIN\TOMCAT33.NCF file and add the
following switch to the Java command line:
-Xmx128m
128 represents the heap memory (in MB) that Tomcat will use. You can go as
high as 400 for this parameter. To change the heap memory to 400 MB, your
Java command line would look similar to the following:
java -Xmx400m -envCWD=$TOMCAT_HOME -classpath
$TOMCAT_CLASSPATH -Dtomcat.home=SYS:\tomcat\33
org.apache.tomcat.startup.Main -f sys:/tomcat/33/conf/
nwserver.xml %1
To determine the heap memory that Tomcat is currently using, enter the
following at the server console:
: java -show
This command will return a process number such as 196.
The following command will show the heap memory setting as well as the
current usage for the heap and physical memory:
: java -showmemory196
Use the number returned from the Java -show command (196 in the above
example).
Deleting All Role Objects
If you delete all the rbsRole objects in iManage without also deleting the tasks,
you can create a new rbsRole object, but the task list will not show any of the
tasks.
You can create a role without any tasks and then modify the role to include
tasks. However, we recommend instead that you re-install the product
packages in order to re-create the removed roles. Use the Install Package task
in iManage to reinstall the product packages.
29
iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6