Investigate Weblogic stop-app-server not having enough time before start-app-server gets triggered

• Type: Bug
• Status: Resolved
• Resolution: Duplicate
• Affects Version/s: 7.0.X, 7.1.X, Master
• Fix Version/s: 7.0.X, 7.1.X, Master
• Component/s: Core Infrastructure
• Labels:
  • 7.2-won't
• Fix Priority: 4

From this log:

   [exec] INFO: ServiceEvent UNREGISTERING {javax.portlet.filter.PortletFilter}={preinitialized.filter=true, bundle.version=3.10.200.v20150831-0856, javax.portlet.name=com_liferay_asset_publisher_web_portlet_MostViewedAssetsPortlet, bundle.id=0, bundle.symbolic.name=org.eclipse.osgi, service.id=8504, service.bundleid=0, service.scope=singleton}
     [exec]        [delete] Deleting: /opt/dev/projects/github/liferay-portal-7.1.x-private/null361704270.properties
     [exec] 
     [exec]     start-app-server:
     [exec] Sep 25, 2018 8:36:42 AM com.liferay.portal.equinox.log.bridge.internal.PortalSynchronousLogListener _log
     [exec] INFO: ServiceEvent UNREGISTERING {com.liferay.portal.kernel.model.Portlet}={bundle.version=3.10.200.v20150831-0856, javax.portlet.name=com_liferay_polls_web_portlet_PollsPortlet, bundle.id=0, bundle.symbolic.name=org.eclipse.osgi, service.id=7592, 

It seems that Weblogic is still UNREGISTERING different services while the start-app-server command gets triggered, so by the time we see services REGISTERED again, it's still not a long enough wait for Weblogic to fully re-start, so when Poshi attempts to hit localhost and sign into portal, portal isn't ready for it.

Then in the final output we see:

java.lang.OutOfMemoryError: GC overhead limit exceeded

I note that Weblogic is also set only to the following memory:

JVM arguments [-Xmx1024m, -XX:MetaspaceSize=512m