Error: "FATAL ERROR: {< SiteWand Bailing Because We Need at Least 4404019200 Max Heap Limit" When Installing 9.0

(Doc ID 1965649.1)

Last updated on MAY 19, 2015

Applies to:

Instantis EnterpriseTrack - Version 9.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : Instantis EnterpriseTrack, version 9.0
After installing Instantis 9.0 the admin server fails to start, switching to a FORCE_SHUTTING_DOWN state.

Error
-----------------------
I. In the AdminServer.log file you can find the following output:
.............................
####<Jan xx, 20xx 8:28:12 PM IST> <Info> <Deployer> <CLDX-455-465> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1421506692533> <BEA-149060> <Module SiteWand.war of application SiteWand successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<Jan xx, 2015 8:28:17 PM IST> <Notice> <WebLogicServer> <CLDX-455-465> <AdminServer> <Thread-1> <> <> <> <1421506697977> <BEA-000388> <JVM called the WebLogic Server shutdown hook. The server will force shutdown now.>
####<Jan xx, 20xx 8:28:17 PM IST> <Alert> <WebLogicServer> <CLDX-455-465> <AdminServer> <Thread-1> <> <> <> <1421506697979> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>.>
####<Jan 17, 20xx 8:28:18 PM IST> <Notice> <WebLogicServer> <CLDX-455-465> <AdminServer> <Thread-1> <> <> <> <1421506698041> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
####<Jan 17, 20xx 8:28:18 PM IST> <Info> <WseeCore> <CLDX-455-465> <AdminServer> <Thread-1> <> <> <> <1421506698043> <BEA-220504> <The Wsee Service is halting>

II. In the stdOutAndErr file you can find the following error:
FATAL ERROR: {< SiteWand bailing because we need at least 4404019200 max heap limit, and we only got 1908932608
THREAD STACK TRACE:
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1364)
at instantis.util.Trace.fatal(Trace.java:484)
at instantis.resourcecache.ResourceCache.(ResourceCache.java:51)
at instantis.resourcecache.CacheManager.initialize(CacheManager.java:31)
at instantis.environment.DBEnvironment.beginTran(DBEnvironment.java:74)
at instantis.environment.DBEnvironment.doBasicDBInitialization(DBEnvironment.java:62)
at instantis.environment.Environment.(Environment.java:93)
at instantis.environment.DBEnvironment.(DBEnvironment.java:26)
at instantis.environment.SiteWandEnvironment.(SiteWandEnvironment.java:43)
at instantis.environment.SiteWandEnvironment.initialize(SiteWandEnvironment.java:32)
at instantis.servlets.BasicServlet.init(BasicServlet.java:45)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:299)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:250)
  ................................

Steps to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:
1. Start the Instantis Domain / Managed Server on a machine that doesn't have enough memory.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms