How to monitor Java memory consumption by the Webaccess Application

  • Document ID:7011449
  • Creation Date:04-Dec-2012
  • Modified Date:28-Jun-2017
    • Micro Focus Products:
      GroupWise

Environment

Novell GroupWise 2014R2
Novell GroupWise 2014
Novell GroupWise 2012

Situation

After long periods of time and high usage, the GroupWise Webaccess Application may seem unresponsive.  This can be a result of a lack of available memory allocated through Java for the process.

Monitoring the numbers will help determine the need to allocate additional memory at startup and increasing the maximum allotted to Java.

Resolution

The following steps only apply to GroupWise 12.0 Service Pack 1 or newer.

To display a running memory usage by the GroupWise Webaccess Application, do the following:
  1. Navigate to /var/opt/novell/groupwise/webaccess and modify the webacc.cfg
  2. Add the following parameter to the end of the file
    Memory.Dump.enabled = true
  3. Restart Tomcat on the server where the Webaccess Application is running by typing rcnovell-tomcat6 restart (on OES) or rctomcat6 restart (on SLES)
  4. After webaccess is running for a short time, the file memory.txt can be found in /var/opt/novell/groupwise/webaccess/logs
    Note: The memory.txt will display data about the memory allocated, used, available and the number of users in at the time.
  5. Open the /etc/sysconfig/tomcat6 and edit the JAVA-OPTS by adding -Xmx4096m so it looks like the line below
    JAVA_OPTS="-Xmx4096m"
    Note:  Numeric options are set with -XX:<option>=<number>. Numbers can include 'm' or 'M' for megabytes, 'k' or 'K' for kilobytes, and 'g' or 'G' for gigabytes (for example, 32k is the same as 32768).
  6. Restart tomcat6 as outlined in step 3