What you will learn in Troubleshooting Java: Read, debug, and optimize JVM applications
Read, debug, and optimize JVM applications
Chapter by chapter
Chapter 1: Revealing an app’s obscurities
This introduction explains why efficient code investigation matters and clarifies how developers use the term debugging.
What you learn in chapter 1 →Chapter 2: Understanding your app’s logic through debugging techniques
This introduction defines a debugger and explains its role in understanding complex code.
What you learn in chapter 2 →Chapter 3: Finding problem root causes using advanced debugging techniques
This introduction previews advanced debugger approaches for investigating code more efficiently.
What you learn in chapter 3 →Chapter 4: Debugging apps remotely
The introduction explains why environment-specific problems may require remote debugging, using entropy-related slowness as an example.
What you learn in chapter 4 →Chapter 5: Making the most of logs: Auditing an app’s behavior
This introduction explains how logs help investigate application behavior, what a useful log message contains, and why logs are a good starting point for investigations.
What you learn in chapter 5 →Chapter 6: Identifying resource consumption problems using profiling techniques
This introduction describes how a profiler can help investigate difficult JVM application problems by revealing resource use, thread status, and executing code.
What you learn in chapter 6 →Chapter 7: Finding hidden issues using profiling techniques
Introduces profiling as a way to investigate execution in hard-to-read applications and previews the chapter’s techniques.
What you learn in chapter 7 →Chapter 8: Using advanced visualization tools for profiled data
This introduction describes call graphs and flame graphs as investigation views and explains why the chapter uses JProfiler alongside prior VisualVM techniques.
What you learn in chapter 8 →Chapter 9: Investigating locks in multithreaded architectures
This introduction previews techniques for investigating execution and performance in multithreaded applications and identifies prerequisite threading knowledge.
What you learn in chapter 9 →Chapter 10: Investigating deadlocks with thread dumps
This introduction explains deadlocks and why thread dumps help investigate an unresponsive JVM process.
What you learn in chapter 10 →Chapter 11: Finding memory-related issues in an app’s execution
This introduction explains the consequences of poor memory management and why heap dumps can help investigate crashes.
What you learn in chapter 11 →Chapter 12: Investigating apps’ behaviors in large systems
This introduction explains why investigating large systems requires looking beyond the behavior of individual applications.
What you learn in chapter 12 →Concepts explained in this book
- profilerA software analysis tool that measures program execution, such as time spent in code, to help identify performance problems.
- samplingSampling is a profiling technique that observes selected parts of a program’s execution to reveal its behavior.
- debuggerA software tool that lets a developer inspect and control a program's execution to examine its behavior or diagnose faults.
- profilingThe practice of gathering information about a program's execution to understand its performance or behavior.
- overall execution timeThe elapsed time for which a thread has been alive.
- remote debuggingDebugging a program by inspecting or controlling its execution from a different environment or machine.
- thread dumpA snapshot of the threads in a running program and their states and stack traces.
- code analysisThe examination of source code to understand program behavior or investigate a possible cause of a problem.
- heap dumpA snapshot of the objects and related information present in a Java heap at a particular time.
- memory leakA software problem in which an application fails to deallocate data it no longer needs, causing free memory to diminish over time.
- resource utilizationThe amount of computing resources, such as processor time or memory, used by a system or application.
- logA record of events or messages generated during software execution.
- CPU timeThe time a program spends executing instructions on the CPU.
- instrumentationA technique that inserts or applies probes to program execution to collect runtime information.
- breakpointA breakpoint is a selected point in a program where a debugger pauses execution.
- JProfilerJProfiler is a commercial profiling tool for Java applications.
- VisualVMVisualVM is a visual tool for monitoring and troubleshooting Java applications, including their threads and resource usage.
- loggingLogging is the recording of events or information produced during a program's execution.
- debugger agentA runtime component attached to an application that enables a debugger to connect and control its execution.
- performance issueA problem in an application’s use of resources or delivery of service, including but not limited to slow responses.
- stack traceA representation of the sequence of method calls active at a particular point in a program's execution.
- connection leakA condition in which a database connection is not closed or released after use, leaving it unavailable for other operations.
- log monitoring toolSoftware that collects and displays application log events to help investigate system behavior and problems.
- lockingA synchronization mechanism that controls concurrent access to a protected resource or code region.
- debuggingThe process of investigating software to identify and understand defects or unexpected behavior.
- latencyDelay in an application's operations or responses, often caused by waiting for input or output.
- CPU usageA measure of the processor resources consumed by a process or application over time.
- zombie threadA thread that remains open and runs without purpose after it is no longer needed.
- drop frameA debugger operation that removes one or more active call-stack frames, allowing execution to return to an earlier call and replay it.
- conditional breakpointA debugger breakpoint configured to evaluate a condition or perform an action, such as logging, without necessarily pausing program execution.
- lock monitoringProfiling that records lock-related activity, including blocked threads and the monitors involved.
- SentrySentry is an application monitoring platform that captures and displays errors and other events from software applications.
- jdbc profilingProfiling that intercepts database queries sent through the Java Database Connectivity API.
- Log4jA Java logging library for recording application events with configurable levels, outputs, and formats.
- synchronizedA Java language construct that restricts execution of a code block so that only one thread at a time can hold its associated monitor.
- memory usageA measure of the memory occupied by a process or application.
- interceptorAn aspect is a modular unit of cross-cutting logic that can augment the execution of selected methods under specified conditions.
- runtime variable modificationRuntime variable modification is changing a program variable’s value while the program is paused during debugging.
- flame graphA visualization of an execution stack in which methods are arranged by call level and their widths indicate relative execution time.
- Step IntoA debugger action that enters a method or instruction called at the current execution point.
- Step OutA debugger action that resumes execution until the current method exits, then pauses in the calling context.
- Step OverA debugger action that executes the current line without entering called methods and pauses at the next line in the current method.
- Object Query LanguageOQL is a query language for retrieving and analyzing objects and references in a Java heap dump.
- call graphA visual representation of execution data that shows relationships between objects and method calls.
- postmortem investigationAn investigation of an application problem using data collected after the application has crashed or stopped.
- thread lockA condition in which a thread cannot continue because it must wait for another thread or access to a synchronized resource.
- external changeA change to state outside an application's internal memory that cannot be undone merely by rewinding its debugger execution.
- N + 1 query problemA performance problem in which retrieving a collection triggers one initial query followed by a separate query for each retrieved record.
- method invocation countThe number of times a method is called during program execution.
- multithreaded programA multithreaded architecture is a program design in which multiple threads execute concurrently.
- fault injectionA testing technique that deliberately introduces faults into a system to reproduce behavior that is otherwise difficult to observe.
- code navigation operationA debugger action that advances or redirects program execution through code.
- waiting threadA thread suspended while awaiting notification from the monitor on which it is waiting.
- waiting timeThe amount of time a thread spends waiting rather than executing.
- deadlockA condition in which threads wait indefinitely for resources or actions held by one another, preventing progress.
- starvationA condition in which a thread is repeatedly denied access to execution or resources it needs to make progress.
- NoSQL databaseA database that uses a nonrelational data model rather than the relational model.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.
