<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-1476 StackOverflowError thrown during WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1476 StackOverflowError thrown during WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup</link><pubDate>Thu, 01 Nov 2018 15:35:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Current Revision posted to Appian Knowledge Base by Jordan Horwat on 11/1/2018 3:35:08 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Linux:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart WebLogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Windows:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.bat &lt;/code&gt;and locate the following line:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart WebLogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian using WebLogic as the application server.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>KB-1476 StackOverflowError thrown during WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/22</link><pubDate>Wed, 31 Jan 2018 00:43:33 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 22 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 12:43:33 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Linux:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart WebLogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Windows:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.bat &lt;/code&gt;and locate the following line:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart WebLogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian using WebLogic as the application server.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/21</link><pubDate>Wed, 31 Jan 2018 00:35:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Tom Ryan</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 21 posted to Appian Knowledge Base by Tom Ryan on 1/31/2018 12:35:08 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&lt;/p&gt;
&lt;p&gt;On Linux:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart weblogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;On Windows:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.bat &lt;/code&gt;and locate the following line:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart weblogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/20</link><pubDate>Wed, 31 Jan 2018 00:33:42 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Tom Ryan</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 20 posted to Appian Knowledge Base by Tom Ryan on 1/31/2018 12:33:42 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&lt;/p&gt;
&lt;p&gt;On Linux:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart weblogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;On Windows:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.bat &lt;/code&gt;and locate the following line:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows:&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Restart weblogic to deploy the change.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/19</link><pubDate>Mon, 29 Jan 2018 23:47:09 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 19 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 11:47:09 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; On Windows (&lt;code&gt;setDomainEnv.bat&lt;/code&gt;),&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt; becomes &lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/18</link><pubDate>Mon, 29 Jan 2018 23:46:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 11:46:36 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; On Windows (&lt;code&gt;setDomainEnv.bat&lt;/code&gt;),&lt;code&gt;&amp;nbsp;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt; becomes &lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/17</link><pubDate>Mon, 29 Jan 2018 23:46:10 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 17 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 11:46:10 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; On Windows (&lt;code&gt;setDomainEnv.bat&lt;/code&gt;),&lt;code&gt;&amp;nbsp;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt; becomes&lt;code&gt; set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/16</link><pubDate>Mon, 29 Jan 2018 23:45:31 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 11:45:31 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open&amp;nbsp;&lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;and locate the following line: &lt;code&gt;JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS}&amp;quot; &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Update the line as follows:&lt;code&gt; JAVA_OPTIONS=&amp;quot;${JAVA_OPTIONS} -Xss4m&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; On Windows (&lt;code&gt;setDomainEnv.bat&lt;/code&gt;),&amp;nbsp;&lt;code&gt;set JAVA_OPTIONS=%JAVA_OPTIONS%&lt;/code&gt; becomes&lt;code&gt; set JAVA_OPTIONS=%JAVA_OPTIONS% -Xss4m&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/15</link><pubDate>Mon, 29 Jan 2018 20:27:25 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Tom Ryan</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 15 posted to Appian Knowledge Base by Tom Ryan on 1/29/2018 8:27:25 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present when the JVM stack size is set to 4MB then increasing the stack further is unlikely to resolve the issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is performing a high level of recursion).&lt;/p&gt;
&lt;p&gt;If the issue is resolved after increasing the stack size to 4MB, reduce the JVM stack as much as possible without triggering the error as setting the stack size unnecessarily high may have a performance impact. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/14</link><pubDate>Mon, 29 Jan 2018 20:21:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Tom Ryan</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 14 posted to Appian Knowledge Base by Tom Ryan on 1/29/2018 8:21:24 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can also happen for valid configurations if the JVM stack size is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/13</link><pubDate>Mon, 29 Jan 2018 19:29:04 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 1/29/2018 7:29:04 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;WebLogic gets stuck on startup and prints the following errors in the application server log:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can happen if the JVM stack is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error. In previous tests, 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed:&amp;nbsp;January 2018&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/12</link><pubDate>Mon, 29 Jan 2018 08:36:28 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 12 posted to Appian Knowledge Base by Jack Chen on 1/29/2018 8:36:28 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can happen if the JVM stack is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, in previous tests 512K has been seen to be optimum. However, every environment is unique and extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/11</link><pubDate>Mon, 29 Jan 2018 08:35:40 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 11 posted to Appian Knowledge Base by Jack Chen on 1/29/2018 8:35:40 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can happen if the JVM stack is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;-Xss&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;-XX:ThreadStackSize&lt;/code&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, in previous tests 512K has been seen to be optimum, however, every environment is unique extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX StackOverflowError thrown upon WebLogic startup</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/10</link><pubDate>Mon, 29 Jan 2018 08:35:09 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 10 posted to Appian Knowledge Base by Jack Chen on 1/29/2018 8:35:09 AM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by unterminated recursion, where the same errors are being repeated over and over again. This can happen if the JVM stack is too small.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;code&gt;&lt;strong&gt;-Xss&lt;/strong&gt;&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code&gt;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt;&lt;/code&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, in previous tests 512K has been seen to be optimum, however, every environment is unique extensive&amp;nbsp;testing is recommended before pushing any changes to production.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic StackOverflowError</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/9</link><pubDate>Sun, 28 Jan 2018 23:00:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 1/28/2018 11:00:12 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again. It can be caused by the&amp;nbsp;JVM stack being too small therefore it throws this error at a long stack trace.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, 512K might be adequate.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic Stack Overflow Errors</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/1</link><pubDate>Thu, 25 Jan 2018 17:05:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 5:05:39 PM&lt;br /&gt;
&lt;h1 class="name"&gt;&amp;nbsp;&lt;/h1&gt;
&lt;div class="content"&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;You can&amp;#39;t start Weblogic and it gets stuck on these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again - which can be caused by multiple&amp;nbsp;things. In this case, it is caused by the&amp;nbsp;JVM stack being too small therefore it sees a long stack as overflowing.
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS = &amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB, then it&amp;#39;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2&gt;&amp;nbsp;&lt;/h2&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic StackOverflowError</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/8</link><pubDate>Thu, 25 Jan 2018 12:27:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 8 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 12:27:06 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again. It can be caused by the&amp;nbsp;JVM stack being too small therefore it throws this error at a long stack trace.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB it is likely another issue. Examine the stack trace to&amp;nbsp;get insight on why long stack traces are being printed (usually something in the environment is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, 512K might be adequate.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic StackOverflowError</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/7</link><pubDate>Thu, 25 Jan 2018 12:23:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 7 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 12:23:43 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again. It can be caused by the&amp;nbsp;JVM stack being too small therefore it throws this error at a long stack trace.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB, then it&amp;#39;s likely another issue. Examine the stack trace to figure out why there might be script that is printing long stack traces (usually something is looping). If the issue goes away, reduce the JVM stack as much as you can without triggering the error, 512K might be adequate.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic StackOverflowError</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/6</link><pubDate>Thu, 25 Jan 2018 12:21:40 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 6 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 12:21:40 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;Weblogic gets stuck on startup and prints these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again - which can have multiple possible causes. In this case, it is caused by the&amp;nbsp;JVM stack being too small therefore it throws this error at a long stack trace.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB, then it&amp;#39;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.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic Stack Overflow Errors</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/5</link><pubDate>Thu, 25 Jan 2018 12:10:27 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 5 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 12:10:27 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;You can&amp;#39;t start Weblogic and it gets stuck on these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again - which can have multiple possible causes. In this case, it is caused by the&amp;nbsp;JVM stack being too small therefore it throws this error at a long stack trace.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB, then it&amp;#39;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.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item><item><title>[DRAFT] - KB-XXXX How to Deal With Weblogic Stack Overflow Errors</title><link>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup/revision/4</link><pubDate>Thu, 25 Jan 2018 12:08:02 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0652fbb2-e3ca-45fa-b073-f66e0f34db6e</guid><dc:creator>Jack Chen</dc:creator><comments>https://community.appian.com/support/w/kb/791/kb-1476-stackoverflowerror-thrown-during-weblogic-startup#comments</comments><description>Revision 4 posted to Appian Knowledge Base by Jack Chen on 1/25/2018 12:08:02 PM&lt;br /&gt;
&lt;h2 class="name"&gt;Symptoms&lt;/h2&gt;
&lt;div class="content"&gt;
&lt;p&gt;You can&amp;#39;t start Weblogic and it gets stuck on these errors:&lt;/p&gt;
&lt;pre class="code-java"&gt;Error creating bean with name &amp;#39;smartServiceBridgeRegistry&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;reactionFunctionProvider&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;importReaction&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;ixActivityService&amp;#39; 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]: : &lt;br /&gt;Error creating bean with name &amp;#39;pojoDatatypesConfig&amp;#39; 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 &amp;#39;pojoDatatypesConfig&amp;#39; threw exception; nested exception is java.lang.StackOverflowError&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;StackOverflow errors are usually caused by something called&amp;nbsp;unterminated recursion, where the same errors are being repeated over and over again - which can be caused by multiple&amp;nbsp;things. In this case, it is caused by the&amp;nbsp;JVM stack being too small therefore it sees a long stack as overflowing.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Increase the JVM stack size. Set&amp;nbsp;&lt;strong&gt;-Xss&lt;/strong&gt;&amp;nbsp;or&amp;nbsp;&lt;strong&gt;-XX:ThreadStackSize&lt;/strong&gt; to a 4 Megabytes.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Go to &lt;code&gt;&amp;lt;WEBLOGIC_HOME&amp;gt;/&amp;lt;project_name&amp;gt;/domains/&amp;lt;domain_name&amp;gt;/bin/setDomainEnv.sh&lt;/code&gt;&amp;nbsp;(make the corresponding change to &lt;code&gt;setDomainEnv.cmd&lt;/code&gt; if on Windows).&lt;/li&gt;
&lt;li&gt;Set the &lt;code&gt;JAVA_OPTIONS=&amp;quot;..-Xss4m..&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;JAVA_OPTIONS=&amp;quot;-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}&amp;quot;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;&lt;/code&gt;If stack overflow errors are still present with the JVM stack at 4MB, then it&amp;#39;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.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
This article applies to all versions of Appian.
&lt;p&gt;Last Reviewed: Month YYYY&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: weblogic, application server, stackoverflow&lt;/div&gt;
</description></item></channel></rss>