Manual Monitoring Java Applications

• 1. Monitoring a Java Application
  • 1.1 How does eG Enterprise Monitor Java Applications?
    • 1.1.1 Enabling JMX Support for JRE
      • 1.1.1.1 Securing the ‘jmxremote.password’ file
      • 1.1.1.2 Configuring the eG Agent to Support JMX Authentication
    • 1.1.2 Enabling SNMP Support for JRE
  • 1.2 The Java Transactions Layer
    • 1.2.1 Java Transactions Test
      • 1.2.1.1 How does eG Perform Java Transaction Monitoring?
  • 1.3 The JVM Internals Layer
    • 1.3.1 JMX Connection to JVM
    • 1.3.2 JVM File Descriptors Test
    • 1.3.3 Java Classes Test
    • 1.3.4 JVM Garbage Collections Test
    • 1.3.5 JVM Memory Pool Garbage Collections Test
      • 1.3.5.1 Enabling GC Logging
    • 1.3.6 JVM Threads Test
      • 1.3.6.1 Accessing Stack Trace using the STACK TRACE link in the Measurements Panel
  • 1.4 The JVM Engine Layer
    • 1.4.1 JVM Cpu Usage Test
    • 1.4.2 JVM Memory Usage Test
    • 1.4.3 JVM Uptime Test
    • 1.4.4 JVM Leak Suspects Test
  • 1.5 What the eG Enterprise Java Monitor Reveals?
    • 1.5.1 Identifying and Diagnosing a CPU Issue in the JVM
    • 1.5.2 Identifying and Diagnosing a Thread Blocking Issue in the JVM
    • 1.5.3 Identifying and Diagnosing a Thread Waiting Situation in the JVM
    • 1.5.4 Identifying and Diagnosing a Thread Deadlock Situation in the JVM
    • 1.5.5 Identifying and Diagnosing Memory Issues in the JVM
    • 1.5.6 Identifying and Diagnosing the Root-Cause of Slowdowns in Java Transactions
• 2. Conclusion