English | MP4 | AVC 1280×720 | AAC 44KHz 2ch | 57 Lessons (7h 36m) | 1.16 GB
Effectively reading and understanding existing code is a developer’s superpower. In this book, you’ll master techniques for code profiling, advanced debugging, and log evaluation to find and fix bugs and performance problems.
In Troubleshooting Java: Read, debug, and optimize JVM applications you will learn how to:
- Determine what code does the first time you see it
- Expose code logic problems
- Evaluate heap dumps to find memory leaks
- Monitor CPU consumption to optimize execution
- Use thread dumps to find and solve deadlocks
- Easily follow a service-oriented or microservices system
- Properly use logging to better understand Java app execution
- Use Java debuggers efficiently
Searching for bugs, detangling messy legacy code, or evaluating your codebase for new features sucks up much of a developer’s time. Troubleshooting Java: Read, debug, and optimize JVM applications teaches code investigation techniques that will help you efficiently understand how Java apps work, how to optimize them, and how to fix the bugs that break them. You’ll go from the basics of debugging to advanced methods for locating problems in microservices architectures, and save yourself hours—or even days—of time. Each new technique is explained with lively illustrations and engaging real-world examples.
Fact: Over the course of your career, you’ll spend far more time reading code than you will writing it. The code investigation skills in this book will radically improve your efficiency in understanding and improving Java applications.
Troubleshooting Java: Read, debug, and optimize JVM applications presents practical techniques for exploring and repairing unfamiliar code. In it, you’ll learn timesaving practices for discovering hidden dependencies, discovering the root causes of crashes, and interpreting unexpected results. Go beyond profiling and debugging and start understanding how Java applications really work.
What’s Inside
- Determine what code does the first time you see it
- Evaluate heap dumps to find memory leaks
- Monitor CPU consumption to optimize execution
- Use thread dumps to find and solve deadlocks
- Uncover glitches in code logic
- Locate intermittent runtime problems
Table of Contents
1 Part 1. The basics of investigating a codebase
2 Revealing an app’s obscurities
3 Demystifying the unexpected output
4 Clarifying slowness
5 Understanding your app’s logic through debugging techniques
6 Investigating code with a debugger
7 What is the execution stack trace, and how do I use it
8 Navigating code with the debugger
9 Finding problem root causes using advanced debugging techniques
10 Dynamically altering the investigation scenario
11 Rewinding the investigation case
12 Debugging apps remotely
13 Investigating in remote environments
14 Finding issues in remote environments
15 Making the most of logs Auditing an app’s behavior
16 Using exception stack traces to identify what calls a method
17 Defining logging levels and using logging frameworks
18 Problems caused by logging and how to avoid them
19 Part 2. Deep analysis of an app’s execution
20 Identifying resource consumption problems using profiling techniques
21 Using a profiler
22 Observing the CPU and memory usage
23 Identifying memory leaks
24 Finding hidden issues using profiling techniques
25 Sampling to observe executing code
26 Profiling to learn how many times a method executed
27 Using a profiler to retrieve SQL queries not generated by a framework
28 Using the profiler to get the SQL queries generated by a framework
29 Using the profiler to get programmatically generated SQL queries
30 Using advanced visualization tools for profiled data
31 Detecting problems with JDBC connections
32 Understanding the app’s code design using call graphs
33 Investigating locks in multithreaded architectures
34 Analyzing thread locks
35 Analyzing waiting threads
36 Investigating deadlocks with thread dumps
37 Reading thread dumps
38 Reading plain-text thread dumps
39 Finding memory-related issues in an app’s execution
40 Sampling and profiling for memory issues
41 Using heap dumps to find memory leaks
42 Reading a heap dump
43 Using the OQL console to query a heap dump
44 Part 3. Finding problems in large systems
45 Investigating apps’ behaviors in large systems
46 Using HTTP client probes to observe HTTP requests the app sends
47 The relevance of integrated log monitoring
48 Using deployment tools in investigations
49 Tools you’ll need
50 Opening a project
51 Recommended further reading
52 Understanding Java threads
53 Synchronizing threads
54 Common issues in multithreaded architectures
55 Memory management in Java apps
56 The stack used by threads to store local data
57 The heap the app uses to store object instances
Resolve the captcha to access the links!