book

Troubleshooting Java

Name: Troubleshooting Java
Author: Laurentiu Spilca
ISBN: 9781617299773

by Laurentiu Spilca

April 2023

Intermediate to advanced

328 pages

8h 31m

English

Manning Publications

Read now

Unlock full access

inside front cover
Tips for applying investigation techniques
Troubleshooting Java
Copyright
contents
front matter
prefaceacknowledgmentsabout this bookWho should read this bookHow this book is organized: A roadmapAbout the codeliveBook discussion forumAuthor onlineabout the authorabout the cover illustration
Part 1. The basics of investigating a codebase
1 Revealing an app’s obscurities
1.1 How to more easily understand your app1.2 Typical scenarios for using investigation techniques1.2.1 Demystifying the unexpected output1.2.2 Learning certain technologies1.2.3 Clarifying slowness1.2.4 Understanding app crashes1.3 What you will learn in this bookSummary
2 Understanding your app’s logic through debugging techniques
2.1 When analyzing code is not enough2.2 Investigating code with a debugger2.2.1 What is the execution stack trace, and how do I use it?2.2.2 Navigating code with the debugger2.3 When using the debugger might not be enoughSummary
3 Finding problem root causes using advanced debugging techniques
3.1 Minimizing investigation time with conditional breakpoints3.2 Using breakpoints that don’t pause the execution3.3 Dynamically altering the investigation scenario3.4 Rewinding the investigation caseSummary
4 Debugging apps remotely
4.1 What is remote debugging?4.2 Investigating in remote environments4.2.1 The scenario4.2.2 Finding issues in remote environmentsSummary

5 Making the most of logs: Auditing an app’s behavior
5.1 Investigating issues with logs5.1.1 Using logs to identify exceptions5.1.2 Using exception stack traces to identify what calls a method5.1.3 Measuring time spent to execute a given instruction5.1.4 Investigating issues in multithreaded architectures5.2 Implementing logging5.2.1 Persisting logs5.2.2 Defining logging levels and using logging frameworks5.2.3 Problems caused by logging and how to avoid them5.3 Logs vs. remote debuggingSummary
Part 2. Deep analysis of an app’s execution
6 Identifying resource consumption problems using profiling techniques
6.1 Where would a profiler be useful?6.1.1 Identifying abnormal usage of resources6.1.2 Finding out what code executes6.1.3 Identifying slowness in an app’s execution6.2 Using a profiler6.2.1 Installing and configuring VisualVM6.2.2 Observing the CPU and memory usage6.2.3 Identifying memory leaksSummary
7 Finding hidden issues using profiling techniques
7.1 Sampling to observe executing code7.2 Profiling to learn how many times a method executed7.3 Using a profiler to identify SQL queries an app executes7.3.1 Using a profiler to retrieve SQL queries not generated by a framework7.3.2 Using the profiler to get the SQL queries generated by a framework7.3.3 Using the profiler to get programmatically generated SQL queriesSummary
8 Using advanced visualization tools for profiled data
8.1 Detecting problems with JDBC connections8.2 Understanding the app’s code design using call graphs8.3 Using flame graphs to spot performance problems8.4 Analyzing queries on NoSQL databasesSummary
9 Investigating locks in multithreaded architectures
9.1 Monitoring threads for locks9.2 Analyzing thread locks9.3 Analyzing waiting threadsSummary
10 Investigating deadlocks with thread dumps
10.1 Getting a thread dump10.1.1 Getting a thread dump using a profiler10.1.2 Generating a thread dump from the command line10.2 Reading thread dumps10.2.1 Reading plain-text thread dumps10.2.2 Using tools to better grasp thread dumpsSummary
11 Finding memory-related issues in an app’s execution
11.1 Sampling and profiling for memory issues11.2 Using heap dumps to find memory leaks11.2.1 Obtaining a heap dump11.2.2 Reading a heap dump11.2.3 Using the OQL console to query a heap dumpSummary
Part 3. Finding problems in large systems
12 Investigating apps’ behaviors in large systems
12.1 Investigating communication between services12.1.1 Using HTTP server probes to observe HTTP requests12.1.2 Using HTTP client probes to observe HTTP requests the app sends12.1.3 Investigating low-level events on sockets12.2 The relevance of integrated log monitoring12.3 Using deployment tools in investigations12.3.1 Using fault injection to mimic hard-to-replicate issues12.3.2 Using mirroring to facilitate testing and error detectionSummary
Appendix A. Tools you’ll need
Appendix B. Opening a project
Appendix C. Recommended further reading
Appendix D. Understanding Java threads
D.1 What is a thread?D.2 A thread’s life cycleD.3 Synchronizing threadsD.3.1 Synchronized blocksD.3.2 Using wait(), notify(), and notifyAll()D.3.3 Joining threadsD.3.4 Blocking threads for a defined timeD.3.5 Synchronizing threads with blocking objectsD.4 Common issues in multithreaded architecturesD.4.1 Race conditionsD.4.2 DeadlocksD.4.3 LivelocksD.4.4 StarvationD.5 Further reading
Appendix E. Memory management in Java apps
E.1 How the JVM organizes an app’s memoryE.2 The stack used by threads to store local dataE.3 The heap the app uses to store object instancesE.4 The metaspace memory location for storing data types
index
inside back cover

Content preview from Troubleshooting Java

Part 1. The basics of investigating a codebase

As a software developer, working on real-world apps often involves investigating how your code works. You have to understand the app’s behavior when fixing problems as well as when implementing new features. You use several techniques for this purpose, such as debugging, logging, profiling, and so on, which we will analyze deeply in this book.

In part 1, we start with the first techniques a developer is exposed to: debugging and logging. When working on an app, a developer must often engage in debugging. For example, say you have a small piece of code, and you need to understand how it works. You use the debugger to pause the application’s execution and dive deep into how the app processes the data. ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781617299773Publisher Support Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Troubleshooting Java

by Laurentiu Spilca

Part 1. The basics of investigating a codebase

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.