Linux problem determination

This section describes problem determination on Linux®.

Use the man command to obtain reference information about many of the commands mentioned in this set of topics.

Setting up and checking your Linux environment
Linux operating systems undergo a large number of patches and updates.
General debugging techniques
This section provides a guide to the diagnostic tools and Linux commands that can be useful when you are diagnosing problems that occur with the Linux JVM.
Diagnosing crashes
Many approaches are possible when you are trying to determine the cause of a crash. The process typically involves isolating the problem by checking the system setup and trying various diagnostic options.
Debugging hangs
A hang is caused by a wait (also known as a deadlock) or a loop (also known as a livelock). A deadlock sometimes occurs because of a wait on a lock or monitor. A loop can occur similarly or sometimes because of an algorithm making little or no progress towards completion.
Debugging memory leaks
If dynamically allocated objects are not freed at the end of their lifetime, memory leaks can occur. When objects that should have had their memory released are still holding memory and more objects are being created, the system eventually runs out of memory.
Debugging performance problems on Linux
Locating the causes of poor performance is often difficult. Although many factors can affect performance, the overall effect is generally perceived as poor response time or slow execution of your program.
MustGather information for Linux
When a problem occurs, the more information known about the state of the system environment, the easier it is to reach a diagnosis.

Parent topic: Problem determination