Are you seeing something like this in your weblogic startup?
***************************************************************************
The WebLogic Server encountered a critical failure
Reason: PermGen space
***************************************************************************
Exception in thread “main”
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread “main”
or
WatchRule: (SEVERITY = ‘Error’) AND ((MSGID = ‘WL-101020’) OR (MSGID = ‘WL-101017’) OR (MSGID = ‘WL-000802’) OR (MSGID = ‘BEA-101020’) OR (MSGID = ‘BEA-101017’) OR (MSGID = ‘BEA-000802’))
WatchData: DATE = Jan 7, 2016 11:46:34 AM EST SERVER = spidmd07_admin MESSAGE = [ServletContext@98678761[app:em module:/em path:/em spec-version:2.5]] Root cause of ServletException.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.apache.myfaces.trinidadinternal.skin.SkinCSSParser._splitString(SkinCSSParser.java:180)
or
<Jan 7, 2016 11:46:13 AM EST> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 1.9.2>
<Jan 7, 2016 11:46:13 AM EST> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 532>
<Jan 7, 2016 11:46:33 AM EST> <Warning> <oracle.mds> <BEA-000000> <A call to flushChanges on the current MDSSession does not specify the correct transaction key>
<Jan 7, 2016 11:46:33 AM EST> <Error> <oracle.adfinternal.controller.application.AdfcExceptionHandler> <ADFC-50018> <ADFc: No exception handler was found for an application exception.
java.lang.OutOfMemoryError: GC overhead limit exceeded
And of course you changed your heap size, but no-go?
You can fix this problem by adding another magic environment variable in setDomainEnvsh:
USER_MEM_ARGS=”-Xms512m -Xmx512m”
export USER_MEM_ARGS
*MAGIC*