This article discusses simulating thread BLOCKED states in chaos engineering using a sample program from BuggyApp. It describes how threads are blocked when attempting to acquire a lock on a synchronized method still held by another thread. It also explains diagnosing blocked threads through manual and automated approaches, including using tools like yCrash for analysis.
This article discusses simulating thread leaks in applications, leading to the 'java.lang.OutOfMemoryError: unable to create new native thread' error. It demonstrates a sample program that creates infinite threads, preventing them from exiting. The article also outlines manual and automated approaches to diagnose and analyze these memory issues effectively.
Coming soon!
Lexington Soft Training Academy held a webinar focused on "Accelerating Incident Response To Production Outages of Enterprise JVM Applications." The session covered significant production outages in major enterprises, including analyses of thread dumps, heap dumps, GC logs, and other relevant artifacts from the incidents, aiming to enhance response strategies.
The content discusses the complexity of JVM arguments related to Garbage collection and memory, highlighting seven key arguments that enhance the performance of Java, Scala, and Jython applications. Four videos cover topics like maximum heap size, thread stack size, garbage collection methods, and timeout settings, along with OutOfMemoryError handling.
The article discusses deadlock in multi-threaded applications, defining it as a situation where processes are blocked, each waiting for a resource held by another. It provides an analogy using trains on a shared track that can't proceed due to overlapping resource needs. Sample Java code illustrates deadlock, while troubleshooting methods are described.
This post explains how to quickly find the Java application process ID on Linux and Windows. For Linux, the command "ps -ef | grep java" displays running Java processes and their IDs. On Windows, the "jps" tool shows running Java processes, albeit with limited argument visibility compared to the Linux method.
Eclipse MAT is a crucial tool for analyzing heap dumps, particularly useful in debugging OutOfMemoryError. It distinguishes between two object sizes: Shallow Heap and Retained Heap. A video is available that explains their differences and calculation methods. Watch it for more insights on using Eclipse MAT effectively.
Discover how to resolve OutOfMemoryError issues using the Eclipse MAT tool. This content provides best practices and useful tips for effectively debugging memory problems. For a deeper understanding, watch the accompanying video.
Eclipse MAT is an effective JVM Memory Analysis tool, with a strong recommendation for its stand-alone version over the plugin. Key tips include allocating extra heap space, enabling 'keep unreachable objects' for better visibility, and adjusting data display settings to more readable formats like KB, MB, and GB for easier analysis.