This task describes the steps used to activate the heap monitor. Heap monitor is used with WebSphere Application Server profiles to monitor heap size of a profile in comparison to pool size.
For existing WebSphere Application Server profiles, there is a script available to add the feature. See The heapMonitor script for more information.
You can use the heap monitor feature to monitor the Java Virtual Machine (JVM) heap size of a WebSphere Application Server profile in comparison to pool size. The feature is available for new WebSphere Application Server profiles or profiles that are created.
To check if a WebSphere Application Server profile has the heap monitor enabled and to activate it if necessary, perform the following steps.
/QIBM/ProdData/WebSphere/AppServer/V61/ND/bin/heapMonitor -profileName default -statusThe output should look similar to the following:
WASX7209I: Connected to process "server1" on node MYSERVER using SOAP connector; The type of process is: UnManagedProcess WASX7303I: The following options are passed to the scripting environment and are available as argument that is stored in the argv variable: "[status, server1]" HEAP0002I: The heap monitor is disabled. $
/QIBM/ProdData/WebSphere/AppServer/V61/ND/bin/heapMonitor -profileName default -enableThe output should look similar to the following:
WASX7209I: Connected to process "server1" on node MYSERVER using SOAP connector; The type of process is: UnManagedProcess WASX7303I: The following options are passed to the scripting environment and are available as argument that is stored in the argv variable: "[enable, server1]" HEAP0005I: Enabling the heap monitor... HEAP0003I: The heap monitor has been enabled. $
HEAP MONITOR STARTED FOR 012500/QEJBSVR/SERVER1 IN SUBSYSTEM QWAS61 IN POOL *BASE POOL ID=2 POOLSIZE(B)=1687994368 RESERVED(B)=778240 HEAP TOTAL(B)=202276864 FREE(B)=67037600 USEDHEAP=135239264 OS400.GC.HEAP.SIZE.MAX(KB) =240000000The heap monitor is activated.