Retrieving Monitored Data About Directory Proxy Server by Using the JVM

Directory Proxy Server runs inside a Java Virtual Machine (JVM) and depends on the memory of the JVM machine. To ensure that Directory Proxy Server is running correctly, you must monitor the memory consumption of the JVM machine.

For information about how to tune parameters for the JVM machine, see Hardware Sizing For Directory Proxy Server in Oracle Directory Server Enterprise Edition Deployment Planning Guide.

By default, the heap size of the JVM machine is 1 Gb. Directory Proxy Server should never be swapped-out from main memory. Directory Proxy Server should be configured to use no more than the actual available memory (considering it coexists with other applications and the OS).

The 1Gb size is generic and might not be suitable for all cases. Should you need to modify the heap size, using a ratio of 2/3 of the total heap for the New Generation (-XX:NewSize and -XX:MaxNewSize arguments) produces the best results. Instances created with previous versions of Directory Proxy Server assigned only 250Mb of memory to the heap, and the default Garbage Collector was used. After an upgrade, these values are not modified on existing instances. The following command can be used to set the new tuning on old instances.

$ dpadm set-flags instance-path jvm-args="-Xms1G -Xmx1G -XX:NewSize=683M 
    -XX:MaxNewSize=683M -XX:+UseParNewGC -XX:+UseConcMarkSweepGC"

When Directory Proxy Server is running, you can monitor the heap size of the JVM machine to ensure that it is not running out of memory. To do this, use the standard tools delivered with the Java Development Kit (JDK): $JAVA_HOME/bin/jps and $JAVA_HOME/bin/jstat.

To View the Heap Size of the JVM

You cannot use DSCC to perform this task. Use the command line, as described in this procedure.

• View the heap size of JVM.

  $ dpadm get-flags instance-path jvm-args
      jvm-args: -Xms1G -Xmx1G -XX:NewSize=683M -XX:MaxNewSize=683M -XX:+UseParNewGC 
      -XX:+UseConcMarkSweepGC

To Monitor the Heap Size of JVM When Directory Proxy Server is Running

You cannot use DSCC to perform this task. Use the command line, as described in this procedure.

1. View the PID of your instance of Directory Proxy Server.

   $ jps

2. View the memory used by the JVM machine.

   $ jstat -gcutil PID

   • If the zero column is near to 100%, the JVM machine does not have enough memory.

   • FGC is the number of full garbage collection (GC) events. Garbage collection is expansive.

   • GCT (garbage collection time) is the amount of time spent by the GC.