HPjmeter 4.
© Copyright 2005–2013 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document.....................................................................................4 Intended Audience....................................................................................................................4 Typographic Conventions...........................................................................................................4 Related Information...............................................................................................................
About This Document This document provides updated information about product features, known problems, and workarounds for the 4.3 release of HPjmeter. Intended Audience This document is intended for application administrators and software developers responsible for installing, configuring, and monitoring Java application performance and operation.
HP Part Number Software Version Number Edition Number Publication Date 5992-5900 4.0.00.00 1 May 2009 5992-0756 3.1.0.00 1 June 2008 5991-6758 3.0.01 3 February 2008 5991-6758 3.0.00.00a 2 August 2007 5991-6758 3.0.00 1 November 2006 5991-6687 2.1.00 2 September 2006 5991-5847 2.1.00 1 July 2006 5991-5438 2.0.00 1 March 2006 HP Encourages Your Comments We encourage your comments concerning this document. We are committed to providing documentation that meets your needs.
1 Announcement With its application and Java Virtual Machine (JVM) metrics, HPjmeter helps operators and developers work better together to find and solve application performance problems. Using HPjmeter, you can monitor the behavior of running applications and capture profiling data for analyzing the performance of Java applications. HPjmeter helps you diagnose many types of Java application problems that occur only after a product is deployed.
• ◦ lock delays and contention ◦ garbage collection Set and receive alerts for error conditions and resource consumption: ◦ abnormal thread termination and deadlock, excessive compilation, and memory leak conditions ◦ heap usage, and system and application CPU utilization thresholds ◦ garbage collection duration and finalizer queue length • When running JDK/JRE 5.0.04 (or later versions of 5.0), capture profiling and verbosegc data with zero preparation. • When running JDK/JRE 6.0.
2 New in This Version Various enhancements and defect fixes are included in this release. New Features and Enhancements HPjmeter 4.3 provides the following major enhancements: • A minimum of Java 6 is required to run the HPjmeter console. • HPjmeter provides a shell script (/opt/hpjmeter/bin/hpjmeter) to easily start the HPjmeter console. In version 4.3, the default Java heap size is increased to 512 MB on Microsoft Windows and 1 GB on UNIX systems. Previously, the default heap size was 256MB.
Table 1 Defect Fixes in HPjmeter 4.3 Release (continued) Defect Tracking Number New Behavior in 4.3 Behavior in 4.2 or Older Versions 30s, GC Duration (Minor) >= 2000ms”. Also, the same time units (seconds for Major and milliseconds for Minor) are now used when setting the alert thresholds in the Alert Controller window. Duration (Minor) >= 20.0”. In this case, the 30 is measured in seconds, the 20 is measured in 100s of milliseconds, and the visualizers graph used milliseconds on the Y axis.
3 Known Problems and Workarounds • The JVM agent may not be able to instrument and collect metrics for certain methods. Review the JVM agent log file to identify the methods that were not measured. The path to the JVM agent log file is: /var/opt/hpjmeter/log/HPjmeter.jvmagent_pid.log where pid is the process ID of the associated JVM agent.
4 Compatibility Information and Installation Requirements You can install the full software package using Software Distributor on supported HP-UX versions running on an HP 9000 or Integrity system. The depot should be installed only on a system where a JVM has already been installed. You can also install only the console on a Microsoft Windows system or on a Linux system.
Table 3 Console Requirements Operating system and architecture The console is a pure Java application, so it should execute on any platform that supports Java. Java Java 6.x or Java 7.x Patches and updates HPjconfig can help you determine which Java patches are recommended or required for best operation of the console on HP-UX. Processor and memory • Minimum 500 MHz processor is recommended. • Minimum 512 MB of memory on Microsoft Windows and 1 GB of memory on UNIX systems is required.
1. Remove HPjmeter files using Software Distributor (SD): $ sudo swremove HPjmeterClient $ sudo swremove HPjmeterMN 2. 3. # removes the console # removes the node agent and JVM agent Check that HP Systems Insight Manager is running. Remove HPjmeter files from HP Systems Insight Manager with this script: $ /opt/hpjmeter/bin/sim_client_cleanup Optionally, you can do step 1 after steps 2 and 3, with the same result. Attaching to the JVM Agent of a Running Application For applications running with Java 6.
3. Specify the JVM agent in your java command. On Java 5.0 and later: $ java -agentlib:jmeter[=options] ... On Java 1.4.2.02 or later 1.4.2 versions: $ java -Xrunjmeter[:options] ... NOTE: If you use the 64-bit JVM agent, you will need to add -d64 to the JVM command line. For example, type $ java —d64 HelloWorld when SHLIB_PATH is $JMETER_HOME/lib/$ARCH and where $ARCH equals PA_RISC2.0W or IA64W.
Starting the Console On Linux To start HPjmeter, type from the command line: $/opt/hpjmeter/bin/hpjmeter The console will be ready to display performance data. Connect to a JVM agent for real-time data, or read a profile data file using the main window tool bar as described in the product documentation.
Want to Know More About Secure Socket Layer Tunneling?: HP-UX IPSec and HP-UX Secure Shell are two HP products that provide secure socket layer tunneling. To learn more: • HP-UX IPSec technical documentation (http://www.hp.com/go/hpux-security-docs) • HP-UX Secure Shell overview and download (http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA) • HP-UX Secure Shell technical documentation (http://www.hp.
Installation Troubleshooting • The HPjmeter installer does not include its own Java runtime. Instead, during installation, the installer locates a Java runtime that is appropriate for running the console, and embeds the path to that JRE into the listed scripts. HPjmeter fails to start if you move or delete the JRE after you install. To fix this problem, you can make either of these changes: ◦ Reinstall a JRE in the expected location specified in the HPjmeter scripts.
5 Support for users Documentation and Support You can find printable PDF versions of the HPjmeter user's guide and the release notes in the installation directory within the doc subdirectory. The latest documentation is also made available at http://www.hp.com/go/hpux-hpjmeter-docs. Problem resolution is available from HP Response Centers worldwide all day every day as part of operating system support contracts. For regional HP Response Center phone numbers, please contact your local HP sales office.
Glossary of Acronyms and Abbreviations CPU Central Processing Unit dynamic attach In HPjmeter, the ability to find and connect to a running JVM on a machine that has the HPjmeter node agent running, but the JVM was started without using HPjmeter options. ephemeral port number a temporary port number assigned from a range of numbers designated for this purpose.
Index Symbols -d64 64-bit JVM agent, 14 A agents requirements, 11 alerts about, 6 application configuring to use JVM agent, 13 C command-line options -d64, 14 compatibility, 11 configure agent library location, 13 JVM agent, 13 configuring library paths, 13 console installing on Linux, 14 installing on Microsoft Windows, 15 launching from HP Systems Insight Manager, 14 requirements, 11 starting from command line on HP-UX, 14 starting on Linux, 15 starting on Microsoft Windows, 15 D data confirming integr
run_simple_jvmagent script, 17 S scripts hpjmeter, 17 run_simple_jvmagent, 17 setup_jvmagent_environment, 17 security, 15 setup_jvmagent_environment script, 17 shared library path Itanium-based systems, 13 SHLIB_PATH configure, 13 support obtaining, 18 T troubleshooting documentation, 18 obtaining support, 18 U user access configuring, 16 X Xbootclasspath configure, 13 21
