Contents

Title and Copyright Information

Preface

• About This Document
• Documentation Accessibility
• Conventions

1 Diagnostics Roadmap

2 Slow JVM Startup

• 2.1 Possible Causes for Slow JVM Startup
• 2.2 Diagnosing Slow JVM Startup
• 2.3 Diagnosing Slow Application Startup
• 2.4 Measuring Timing
• 2.5 Recommended Solutions for Slow JVM Startup

3 Long Latencies

• 3.1 Tune the JVM to Reduce Latency
• 3.2 Troubleshooting Latency Issues
  • 3.2.1 GC Trigger Value Keeps Increasing
  • 3.2.2 GC Reason for Old Collections is Failed Allocations
  • 3.2.3 Long Young-Collection Pause Times
  • 3.2.4 Long Pauses in Deterministic Mode
• 3.3 Contact Oracle Support

4 Low Overall Throughput

5 Performance Degradation

• 5.1 Tune for Performance
• 5.2 Troubleshoot Optimization Problems
• 5.3 Troubleshoot Memory Leak Problems
• 5.4 Contact Oracle Support

6 Crashing JVM

• 6.1 Classify the Crash
  • 6.1.1 Using a Crash File
  • 6.1.2 Determine the Crash Type
• 6.2 Out-Of-Virtual-Memory Crash
  • 6.2.1 Verify the Out-Of-Virtual-Memory Error
  • 6.2.2 Troubleshoot the Out-Of-Virtual-Memory Error
    • 6.2.2.1 Upgrade to the Latest JRockit JVM Release
    • 6.2.2.2 Reduce the Java Heap Size
    • 6.2.2.3 Use the Windows /3GB Startup Option
    • 6.2.2.4 Check for Memory Leaks in JNI Code
    • 6.2.2.5 Record Virtual Memory Usage
    • 6.2.2.6 Contact Oracle Support
• 6.3 Stack Overflow Crash
  • 6.3.1 Verify the Stack Overflow Crash
  • 6.3.2 Troubleshoot a Stack Overflow Crash
    • 6.3.2.1 Application Level Changes
    • 6.3.2.2 Increase the Default Stack Size
    • 6.3.2.3 Make the JRockit JVM More Robust Against Stack Overflow Errors
    • 6.3.2.4 Contact Oracle Support
• 6.4 Crash Caused by Unsupported Linux Configuration
• 6.5 JVM Crash
  • 6.5.1 Crash During Code Generation
    • 6.5.1.1 Identify the Method that Might Have Caused the Code-Generation Crash
    • 6.5.1.2 Verify Whether the Crash is Due to Optimization Problems
    • 6.5.1.3 Exclude the Problem Method from the Optimization Process
    • 6.5.1.4 Check Whether the Problem is Caused by an External Instrumentation Tool
    • 6.5.1.5 Contact Oracle Support
  • 6.5.2 Crash During Garbage Collection
    • 6.5.2.1 Identify the Garbage Collection Crash
    • 6.5.2.2 Upgrade to the Latest Release of the JRockit JVM
    • 6.5.2.3 Try the Following Workarounds
    • 6.5.2.4 Contact Oracle Support

7 Freezing JVM

• 7.1 Diagnosing Where the Freeze is Occurring
• 7.2 Troubleshooting a Java Application Freeze
• 7.3 Troubleshooting a JVM Freeze
  • 7.3.1 Force the JRockit JVM to Crash (on a Linux System)
  • 7.3.2 Force the JRockit JVM to Crash (on a Windows System)
  • 7.3.3 Collecting State Information When the JRockit JVM is Running as a Service

8 About Crash Files

• 8.1 Differences Between Text and Binary Crash Files
• 8.2 Enabling Crash Files
• 8.3 Specifying the Location of the Crash Files
• 8.4 Specifying the Size of the Binary Crash File
• 8.5 Disabling Crash Files
• 8.6 Troubleshooting by Using the Text Crash File
  • 8.6.1 Symptoms to Look for
  • 8.6.2 Example of a Text Dump File
• 8.7 Generating Java Heap Dumps in the HPROF Binary Format

9 Contacting Oracle for Support