HP-UX系统下的Java故障排查指南

需积分: 0 127 浏览量更新于2025-01-09 收藏 752KB PDF 举报

“java troubleshooting guide for HP-UX.pdf”是一份由Hewlett-Packard Development Company在2007年7月发布的第三版技术文档，主要针对在HP-UX操作系统上运行Java时可能遇到的问题提供解决方案。该指南包含了诊断、监控工具和选项，以及对Java在HP-UX系统上出现问题时的处理策略。文档内容涵盖了以下几个关键知识点： 1. **关于此文档**：这部分可能介绍了文档的目的、适用人群和阅读指南，帮助用户理解如何有效地利用这份文档来解决Java在HP-UX环境中的问题。 2. **诊断和监控工具及选项**：这是文档的核心部分，详细列出了各种用于分析和监控Java运行状况的工具和选项。这可能包括： - **HP-UX Java工具和选项表格**：列出了一系列专为HP-UX设计的Java工具和命令行选项，用于调试、性能分析和问题定位。 - **崩溃分析工具**：这些工具如core dump分析器，用于解析程序崩溃时产生的核心转储文件，以确定导致崩溃的原因。 - **挂起和死锁进程**：文档可能提供了识别和解决Java进程挂起或死锁的方法，这可能涉及线程分析和内存管理策略。 - **致命错误处理**：介绍如何应对Java应用程序中出现的严重错误，可能包括日志分析、异常处理机制和错误恢复策略。 3. **监控**：这部分可能涉及了性能监控和日志记录，帮助用户实时了解Java应用的健康状况，预防潜在问题。 4. **法律条款**：文档强调了软件的版权信息，指出只有获得HP的许可才能拥有、使用或复制，并提到了对于美国政府用户，软件和服务遵循供应商的标准商业许可证。此外，文档明确表示不提供额外的保修，且免除了HP因技术或编辑错误或遗漏所可能导致的责任。 5. **UNIX商标**：提及UNIX是The Open Group注册商标，表明文档内容与UNIX标准和规范有关。这份指南对于在HP-UX上管理和维护Java环境的技术人员来说，是一份非常实用的参考资料，它提供了丰富的故障排查和优化方法，有助于提升Java应用的稳定性和性能。

1 Diagnostic and Monitori ng Tools and Options

This chapter describes the tools and options available for postmortem diagnostics, analysis of

hung/deadlocked processes, monitoring memory usage, and performance monitoring.

The tools and options are listed in tables by their respective functions in the first section of this

chapter. Many of them are listed in multiple tables since they can be used for multiple functions.

The tools and options are described in detail with examples, where applicable, in the remaining

sections of this chapter. All the tools and options described in this chapter are either included in

the Java 2 Platform Standard Edition Development Kit (JDK 1.5+), are included with

Hewlett-Packard's Java product, or are available for download at the Go Java! website:

http://www

.hp.com/products1/unix/java

1.1 HP-UX Java Tools and Options Tables

The tools and options are categorized into the following table groupings:

• Crash Analysis Tools

• Hung and Deadlocked Processes

• Fatal Error Handling

• Monitoring Memory Use

• Performance Tools

• Miscellaneous Tools and Options

• JDK Tools Not Available on HP-UX

1.1.1 C r a s h A n a l y s i s To o l s

Several of the options and tools described in this chapter are designed for postmortem diagnostics.

These are the options and tools that can be used to obtain additional information if an application

crashes. This analysis may either be done at the time of the crash or at a later time using

information from the core file. In addition to these tools, many other tools have features useful

for crash analysis.

Table 1-1 Tools and Options for Crash Analysis

Description and UsageTool or Option

An HP-supported implementation of the gdb debugger

that has Java support. For simplicity, this document will

refer to wdb/gdb as gdb from this point forward. gdb can

be used to attach to a running process.

wdb/gdb

Contains information obtained at the time of the crash.

Often one of the first pieces of data to examine when a

crash occurs.

Fatal Error Log (hs_err_pid<pid>.log)

Specify filename to use for the fatal error log.-XX:ErrorFile

Specify a sequence of user-supplied scripts or commands

to be executed when a crash occurs.

-XX:OnError

Suspend the process when a crash occurs. Depending on

the user response, it can launch the gdbgdb debugger to

attach to the Java VM.

-XX:+ShowMessageBoxOnError

Java language debugger.jdb

1.1.2 Hung and Deadlocked Processes

The following options and tools can help you debug a hung or deadlocked process:

1.1 HP-UX Java Tools and Options Tables 13

Table 1-2 Tools and Options for Debugging Hung and Deadlocked Processes

Description and UsageTool or Option

An HP-supported implementation of the gdb debugger

that has Java support. For simplicity, this document refers

to wdb/gdb as gdb from this point forward. gdb can be

used to attach to a running process.

wdb/gdb

Used to identify and diagnose performance problems in

Java applications running on HP-UX. It can also be used

to debug thread and heap issues.

HPjmeter

Used to retrieve thread dump information. It also executes

a deadlock detection algorithm and reports any deadlocks

detected involving synchronized code. Heap dumps are

also generated beginning with JDK 1.5.0.05 and SDK

1.4.2.11 when the -XX:+HeapDumpOnCtrlBreak option

is specified.

Ctrl-Break Handler

Used to observe memory allocation in a running Java

application by taking snapshots of the heap over time. It

can be set by providing the -XX:+HeapDump option or

setting the _JAVA_HEAPDUMP environment variable.

-XX:+HeapDump and _JAVA_HEAPDUMP Environment

Variable, starting with JDK 1.5.0.03 and SDK 1.4.2.10

Creates a core image of a running process.gcore (11.31 only)

Java language debugger.jdb

1.1.3 Fatal Error Handling

The following options are useful for retrieving more information when fatal errors occur:

Table 1-3 Options for Fatal Error Handling

Description and UsageOption

Used to specify a sequence of user-supplied scripts or

commands to be executed when a crash occurs.

-XX:OnError

Used to suspend the process when a crash occurs. After

the process is suspended, the user can use gdb to attach

to the Java VM.

-XX:+ShowMessageBoxOnError

Enables dumping of the heap when an out of memory

error condition occurs in the Java VM.

-XX:+HeapDumpOnOutOfMemoryError, starting with

SDK 1.4.2.11 and JDK 1.5.0.04

1.1. 4 M o n i t o ri n g M e m o r y U s e

The following options and tools are useful for monitoring memory usage of running applications:

Table 1-4 Tools and Options for Monitoring Memory Use

Description and UsageTool

Used to identify and diagnose performance problems in

Java applications by examining and monitoring the heap

and threads.

HPjmeter

HP's garbage collection (GC) visualization tool for

analyzing garbage collection activity in a Java program.

HPjtune

Used to observe memory allocation in a running Java

application by taking snapshots of the heap over time. It

can be set by providing the -XX:+HeapDump option or

setting the _JAVA_HEAPDUMP environment variable.

-XX:+HeapDump and _JAVA_HEAPDUMP Environment

Variable, starting with JDK 1.5.0.03 and SDK 1.4.2.10

14 Diagnostic and Monitoring Tools and Options

Table 1-4 Tools and Options for Monitoring Memory Use (continued)

Description and UsageTool

Used to enable logging of garbage collection information.

The HP-only -Xverbosegc option generates additional

GC information that is used by HPjtune. It is preferable

to use -Xverbosegc instead of -verbose:gc.

-Xverbosegc (HP only) and -verbose:gc

This third-party tool may be used to perform Java heap

analysis.

hat

Used to monitor and manage an application launched

with a management agent on a local or remote machine.

jconsole (1.5+ only)

1.1.5 Performance Tools

The following tools are useful for identifying where the application spends its time. Some tools

allow you to monitor performance in real time (dynamic analysis) and other tools allow you to

analyze captured profiling data (static analysis):

Table 1-5 Performance Tools

Description and UsageTool

Use statically collected eprof data to understand where

the application is spending time. Use dynamic real-time

monitoring to identify performance issues.

HPjmeter

HP's GC visualization tool for analyzing garbage

collection activity statically collected in a Java program.

HPjtune

Attaches to the Java VM and collects and logs performance

statistics dynamically.

jstat (1.5+ only)

Launches a simple console tool enabling you to

dynamically monitor and manage an application launched

with a management agent on a local or remote machine.

jconsole (1.5+ only)

Simple static profiler agent used for heap and CPU

profiling.

hprof

1.1.6 Miscellaneous Tools and Options

The following tools and options do not fall into any of the previous categories:

Table 1-6 Miscellaneous Tools and Options

Description and UsageTool or Option

Used to augment the options specified in the Java

command line.

JAVA_TOOL_OPTIONS Environment Variable

Tools include jps, jstat, and jstatd. These tools are

included with JDK 1.5+.

jvmstat Tools

Uses jvmstat technology to provide visualization of

garbage collection activity in the Java VM.

visualgc

Enables logging of class loading and unloading.-verbose:class

Enables logging of JNI (Java Native Interface).-verbose:jni

Performs additional validation on the arguments passed

to JNI functions.

-Xcheck:jni

1.1 HP-UX Java Tools and Options Tables 15

1.1.7 JDK Tools Not Available on HP-UX

Some JDK tools are not available on HP-UX, so they are not described in this document. They

are provided in JavaSoft JDK as unsupported tools. Equivalent functionality is available via gdb

Java support, HPjmeter, and the HeapDump options.

Table 1-7 JDK Tools Not Available on HP-UX

Description and HP-UX AlternativeTool

Prints Java configuration information for a given Java

process, core file, or remote debug server.

jinfo

Prints shared object memory maps or Java heap memory

details of a given process, core file, or remote debug

server. Use the HeapDump options or gdb heap dump

functionality instead.

jmap

Prints a Java stack trace of Java threads for a given Java

process, core file, or remote debug server. Use gdb stack

trace b ack functionality instead.

jstack

Not yet ported to HP-UX.Serviceability Agent (SA)

1.2 Ctrl-Break Handler

A thread dump is printed if the Java process receives a SIGQUIT signal. Therefore, issuing the

command kill -3 <pid> causes the process with id <pid> to print a thread dump to its

standard output. The application continues processing after the thread information is printed.

In addition to the thread stacks, the ctrl-break handler also executes a deadlock detection

algorithm. If any deadlocks are detected, the ctrl-break handler also prints out additional

information on each deadlocked thread. The SIGQUIT signal can also be used to print heap dump

information when using the -XX:+HeapDump or -XX:+HeapDumpOnCtrlBreak options

described further on in this chapter.

Following is an example of output generated when SIGQUIT is sent to a running Java process:

Full thread dump [Thu Oct 12 14:00:56 PDT 2006] (Java HotSpot(TM) Server

VM 1.5.0.03 jinteg:02.13.06-21:25 IA64 mixed mode):

"Thread-3" prio=10 tid=00a78480 nid=24 lwp_id=2669798 runnable [0bfc0000..0bfc0ae0]

at java.lang.Math.log(Native Method)

at spec.jbb.JBButil.negativeExpDistribution(JBButil.java:795)

at spec.jbb.TransactionManager.go(TransactionManager.java:234)

at spec.jbb.JBBmain.run(JBBmain.java:258)

at java.lang.Thread.run(Thread.java:595)

"Thread-2" prio=2 tid=009fb7a0 nid=23 lwp_id=2669797 runnable [0c1c0000..0c1c0b60]

at spec.jbb.Order.dateOrderlines(Order.java:341)

- waiting to lock <444ba618> (a spec.jbb.Order)

at spec.jbb.DeliveryTransaction.process(DeliveryTransaction.java:213)

at spec.jbb.DeliveryHandler.handleDelivery(DeliveryHandler.java:103)

at spec.jbb.DeliveryTransaction.queue(DeliveryTransaction.java:363)

- locked <154927e8> (a spec.jbb.DeliveryTransaction)

at spec.jbb.TransactionManager.go(TransactionManager.java:431)

at spec.jbb.JBBmain.run(JBBmain.java:258)

at java.lang.Thread.run(Thread.java:595)

"Thread-1" prio=10 tid=008ffa80 nid=22 lwp_id=2669796 runnable [0c3c0000..0c3c0de0]

at spec.jbb.infra.Collections.longStaticBTree.get(longStaticBTree.java:1346)

at spec.jbb.Warehouse.retrieveStock(Warehouse.java:307)

at spec.jbb.Orderline.validateAndProcess(Orderline.java:341)

- locked <48563610> (a spec.jbb.Orderline)

at spec.jbb.Order.processLines(Order.java:289)

- locked <48563128> (a spec.jbb.Order)

at spec.jbb.NewOrderTransaction.process(NewOrderTransaction.java:282)

at spec.jbb.TransactionManager.go(TransactionManager.java:278)

at spec.jbb.JBBmain.run(JBBmain.java:258)

at java.lang.Thread.run(Thread.java:595)

"Thread-0" prio=2 tid=00781240 nid=21 lwp_id=2669795 runnable [0c5c0000..0c5c0e60]

at spec.jbb.infra.Util.DisplayScreen.privIntLeadingZeros(DisplayScreen.java:448)

at spec.jbb.infra.Util.DisplayScreen.putDollars(DisplayScreen.java:1214)

at spec.jbb.NewOrderTransaction.secondDisplay(NewOrderTransaction.java:416)

- locked <154d4828> (a spec.jbb.NewOrderTransaction)

at spec.jbb.TransactionManager.go(TransactionManager.java:279)

at spec.jbb.JBBmain.run(JBBmain.java:258)

16 Diagnostic and Monitoring Tools and Options

剩余77页未读，继续阅读

totti19841106

粉丝: 4
资源: 4

HP-UX系统下的Java故障排查指南

JDK18-troubleshooting-guide.pdf

Python库 | troubleshooting-framework-1.3.0.3.tar.gz

JDK9-JSE-Troubleshooting Guide-244.pdf

NetBackup Appliance Troubleshooting Guide - 3.1.pdf

FXOS Troubleshooting Guide for the Firepower 2100.pdf

JDK17-troubleshooting-guide.pdf

JDK16-troubleshooting-guide.pdf

JDK12-troubleshooting-guide.pdf

jdk20-troubleshooting-guide.pdf

JDK15-troubleshooting-guide.pdf

最新资源