Monitor LiveCycle JVM Heap Utilization Using JConsole

The 1.5 (or 5.0) versions of JDKs from Sun (HotSpot), IBM (J9) as well as BEA (JRockit) come with JConsole, a very user-friendly tool that can be used to monitor heap usage within the JVM. It can also be used to monitor a limited number of LiveCycle metrics (such as the number of invocations).

In the next release of LiveCycle (8.2.1, also known as LiveCycle ES Update 1) slated for the latter half of 2008, there will be a lot more LiveCycle JMX metrics you can track. Please see Adobe Technical Guide. Don’t be spooked by the warning you get on opening it (“the author of this document may have chosen to audit your intearactions with it”). It is Adobe LiveCycle Rights Management ES in action.

1) First, you have to re-start JBoss with remote JMX monitoring enabled.
2) Figure out a port that is not used on the server.
3) Add the following entries to JBoss’ run.bat or

rem ————————————–
rem Enable Remote JMX Monitoring
rem ————————————-

for (Linux)

# ————————————-
# Enable Remote JMX Monitoring
# ————————————

4) Run JConsole from the /bin folder of the JDK.

If you are running JConsole on the same server as JBoss, the JVM will be listed in the ‘Local’ tab of the JConsole ‘Connection’ dialog. If JBoss is running on a remote server, click on the ‘Remote’ tab, and provide the IP address and JMX port (50050 in the example above). If is set to true, you would need to provide the userID and password.

5) Click on the ‘Memory’ tab. You will see real-time charts you can display for heap memory usage, non-heap memory usage, and memory allocated to the ‘survivor’, ‘eden’, ‘old generation’ and ‘permanent generation’ memory areas. At the bottom, it will also provide you with the frequency and duration of garbage collections. To learn more about generational heap areas, please see article titled “Tuning Garbage Collection with the 5.0 Java Virtual Machine” at the Sun Developer Network.

Since IBM’s J9 JDK does not implement generational garbage collection, its JConsole display for the ‘Memory’ tab will look slightly different.

Running JConsole is not as intrusive as running full-fledged java profilers such as Quest JProbe. Keeping JConsole running during your functional and/or load testing will provide you with valuable insight on the behavior of LiveCycle.

Clicking on the ‘MBeans’ tab will let you track some LiveCycle-specific metrics. For example, expand the node on the left. Navigate to>XMLFormService->RequestCount->AdobeStat. The value of the ‘Count’ field will tell you how many times the XMLFormService has been invoked since JBoss was started.


اترك رد

Please log in using one of these methods to post your comment: Logo

أنت تعلق بإستخدام حساب تسجيل خروج   /  تغيير )

Google+ photo

أنت تعلق بإستخدام حساب Google+. تسجيل خروج   /  تغيير )

صورة تويتر

أنت تعلق بإستخدام حساب Twitter. تسجيل خروج   /  تغيير )

Facebook photo

أنت تعلق بإستخدام حساب Facebook. تسجيل خروج   /  تغيير )


Connecting to %s

%d مدونون معجبون بهذه: