[DRAFT] - KB-XXXX How to Deal With Weblogic Stack Overflow Errors

You can't start Weblogic and it gets stuck on these errors:

Error creating bean with name 'smartServiceBridgeRegistry' defined in class path resource [com/appiancorp/expr/server/reaction/ReactionSpringConfig.class]: Unsatisfied dependency expressed through constructor argument with index 1 of type [com.appiancorp.core.expr.reaction.ReactionFunctionProvider]: : 
Error creating bean with name 'reactionFunctionProvider' defined in class path resource [com/appiancorp/expr/server/reaction/ReactionSpringConfig.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [java.util.List]: : 
Error creating bean with name 'importReaction' defined in class path resource [com/appiancorp/object/action/ObjectActionSpringConfig.class]: Unsatisfied dependency expressed through constructor argument with index 4 of type [com.appiancorp.ix.activity.IxActivityService]: : 
Error creating bean with name 'ixActivityService' defined in class path resource [com/appiancorp/ix/spring/IxActivitySpringConfig.class]: Unsatisfied dependency expressed through constructor argument with index 4 of type [com.appiancorp.type.config.plugin.PojoDatatypesConfig]: : 
Error creating bean with name 'pojoDatatypesConfig' defined in class path resource [com/appiancorp/type/TypeSpringConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.type.config.plugin.PojoDatatypesConfig]: Factory method 'pojoDatatypesConfig' threw exception; nested exception is java.lang.StackOverflowError

Cause

StackOverflow errors are usually caused by something called unterminated recursion, where the same errors are being repeated over and over again - which can be caused by multiple things. In this case, it is caused by the JVM stack being too small therefore it sees a long stack as overflowing.

Action

Increase the JVM stack size. Set -Xss or -XX:ThreadStackSize to a 4 Megabytes. 

1. Go to <WEBLOGIC_HOME>/<project_name>/domains/<domain_name>/bin/setDomainEnv.sh (make the corresponding change to setDomainEnv.cmd if on Windows).
2. Set the JAVA_OPTIONS = "..-Xss4m.."

For example:

JAVA_OPTIONS="-Duser.timezone=GMT -Dfile.encoding=UTF-8 -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl -Djava.awt.headless=true -Xms512m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError -Dweblogic.log.RedirectStdoutToServerLogEnabled=true -Dweblogic.log.RedirectStderrToServerLogEnabled=true -Xss4m ${JAVA_OPTIONS}"

If stack overflow errors are still present with the JVM stack at 4MB, then it's likely another issue. If the issue goes away, reduce the JVM stack as much as you can without triggering the error, 512K might be adequate.

Affected Versions

Last Reviewed: Month YYYY