Why java.lang.StackOverflowError occurred?

Solution Verified - Updated -

Issue

  • Why Java application server (JBoss EAP or Tomcat) shuts down automatically with StackOverflowError?
  • Why stackoverflow error is seen in the logs when the "session data is being replicated"?
  • Why I'm getting StackOverflowError when deploying EAR file?
  • Why liferay WAR application deployment fails with nested exception is java.lang.StackOverflowError?
  • Why following error is coming in the JBoss "server log" ?
ERROR [org.jboss.mx.loading.LoadMgr3] Not rescheduling failed loading task,
loadTask=org.jboss.mx.loading.ClassLoadingTask@1923ca5{classname: org.omg.ETF._ConnectionLocalBase, requestingThread: Thread[main,5,jboss],
requestingClassLoader: org.jboss.mx.loading.UnifiedClassLoader3@171f189{ url=null ,addedOrder=2}, loadedClass: nullnull, loadOrder: 2147483647,
loadException: java.lang.StackOverflowError, threadTaskCount: 0, state: 1, #CCE: 1}
java.lang.StackOverflowError
at java.lang.Exception.<init>(Exception.java:59)
at java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:65)
...
  • We are having problems with java.lang.StackOverflowError. what exactly needs to be done. Also let us know what all information is required to attach in the support case to confirm this.

  • We are experiencing a StackOverflowError during some kind of serialization the JBoss EAP is performing. The stacktrace is filled up with:

java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1189)
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
  • The exception stacktrace gives no info apart from this method calls logs. Is there any way we can find what the JBoss EAP is trying to serialize? Maybe using some option that enables the full stack trace?

Environment

  • Java
  • Red Hat JBoss Enterprise Application Platform (EAP)
  • Apache Tomcat

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In