This article walks through a real‑world case where adding a new JAR triggers a java.lang.StackOverflowError during Spring application startup, explains how hidden recursive calls in bean initialization cause the overflow, and offers debugging steps and a design‑level fix to prevent the issue.
This article explains the purpose of learning the JVM memory layout, describes each runtime data area—including program counter, VM stack, native method stack, heap, and method area—highlights thread‑private versus shared regions, and provides code samples that trigger StackOverflowError and OutOfMemoryError across different JDK versions.
The article analyzes a StackOverflowError that occurs during Spring application startup after upgrading to JDK 8, tracing the deep bean‑creation call chain caused by extensive use of @Autowired with MyBatis MapperFactoryBean, and recommends upgrading mybatis‑spring and switching to @Resource to prevent the overflow.
The article explains that in Java a single thread hitting stack limits triggers StackOverflowError, while true OutOfMemoryError arises only when multiple threads exhaust the operating system's memory, and it offers practical tips to mitigate such OOM situations.
