The JAX online conference gathers Java and software architecture enthusiasts globally. This year, an architect presented “Let's crash the applications!”, addressing issues like memory leaks, deadlocks, and CPU spikes through sample code. Understanding these triggers can simplify diagnosing and resolving related problems. Presentation slides are provided for reference.
The 'java.lang.System.getProperty()' API allows Java developers to read system properties but can degrade application performance when used in critical code paths due to synchronization issues. A real-world example shows 189 threads getting blocked, impacting response time. Solutions include upgrading to JDK 11 or caching property values for improved performance.
This article on chaos engineering demonstrates how to simulate a CPU spike to 100% using an infinite loop in a Java program with multiple threads. It discusses monitoring CPU consumption using the UNIX tool 'top' and suggests manual and automated root cause analysis methods, highlighting the yCrash tool's effectiveness in identifying the source of the issue.