java.lang.StackOverflowError
The thread’s call stack overflowed — almost always unbounded recursion, sometimes a bidirectional toString/equals/JSON cycle.
Meaning
The stack trace repeats the same few frames. Common non-obvious sources: JPA entities with bidirectional relations in toString()/hashCode() (Lombok @Data), Jackson serialising cycles, and Spring beans calling each other.
Common causes
- Recursion without a terminating condition
- Lombok @Data / toString on bidirectional JPA relations
- Jackson serialising parent ↔ child references
- Very deep (legitimate) recursion on large inputs
⚡ Quick fix
- Find the repeating frames in the trace
- Exclude back-references from toString/equals (
@ToString.Exclude) - Use
@JsonManagedReference/@JsonBackReferenceor DTOs - Convert deep recursion to iteration, or raise
-Xssas a last resort
Detailed fix by platform
Java
- Break JPA/Lombok cycles:java
@Entity @Getter @Setter public class Order { @ManyToOne @ToString.Exclude @EqualsAndHashCode.Exclude @JsonBackReference private Customer customer; }
How to diagnose
- Frames — Which methods repeat?
- Entities — toString/equals/JSON cycles?
- Input size — Legitimately deep recursion?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Java
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026