What's Going Wrong with My JVM?! A Guide to First-Time Failure Diagnosis
It's 2 AM Friday night when you get alerts your primary business application stopped responding and user tickets are piling up. For situations like these, you need to have already captured the data that can help you quickly get a sense of what's going wrong. Yet many production environments don't have such data collection enabled, and some diagnostics have performance costs that are unsuitable for many production applications. In this session, we’ll use some commonly reported Java heap memory problems to show how to collect and analyze some low-cost data to diagnose those problems at first-time failure.
It's 2 AM Friday night when you get alerts your primary business application stopped responding and user tickets are piling up. For situations like these, you need to have already captured the data that can help you quickly get a sense of what's going wrong. Yet many production environments don't have such data collection enabled, and some diagnostics have performance costs that are unsuitable for many production applications. In this session, we’ll use some commonly reported Java heap memory problems to show how to collect and analyze some low-cost data to diagnose those problems at first-time failure.
What's Your Reaction?
![Episode 73 “Immutable Data Beyond Value Classes” [AtA]](https://inside.java/resources/ijp-73--OGaCbzOhnY35SMXr0wfqlA8NOoym9jFUSby61tzkE.jpg)
