A Spring Boot application unexpectedly surged in JVM memory usage from 8GB to 61GB without any deployment or configuration changes. By diagnosing a ZipFile$Source memory leak with yCrash, the team identified excessive caching leading to the leak. By disabling caching and restarting the app, they reduced memory usage to 4GB effectively.
Spring Boot, widely used for Java-based applications, often encounters Metaspace OutOfMemory issues due to high class metadata usage, leaked classes, and inadequate size configuration. Proper JVM adjustments, like increasing Metaspace size and optimizing class loading, alongside tools like yCrash for monitoring, can help troubleshoot and resolve these exceptions effectively.
This article talks about a common problem with Spring Boot applications: database connection leaks. These leaks happen when connections aren't closed properly, which can slow down the system or even cause it to crash. The article sheds some light on how one can find and fix these leaks by looking at errors and network metrics and also suggests solutions like try-with-resources and connection pools to stop leaks from happening in the first place.
