Webview log shows this error repeatedly and disallows connections.
!ENTRY org.eclipse.osgi 4 0
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
at org.eclipse.core.launcher.Main.main(Main.java:44)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)
Ran in <em_home>
./jre/bin/java -jar ./tools/osgi-configurator.cli.jar -d ./product/webview -b ./config/bundles-configuration.txt
which recreated the <em_home>/product/webview/configuration/org.eclipse.equinox.simpleconfigurator and on start up that generated the org.eclipse.core.runtime
org.eclipse.equinox.app, org.eclipse.update directories.
Webview started and was accessible from Chrome.
So the logs are filled of java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
There are number of third-party articles on this.
You could also try to clear osgi cache . Note that the directions changed with 10.8 SP1
While clearing the cache for some reason the earlier instruction was to clear explicitly the cache from EM_HOME\product\enterprisemanager\configuration except config.ini However this will now give a problem to start EM.
The deletion of org.eclipse.equinox.simpleconfigurator caused this issue.
The org.eclipse.equinox.simpleconfigurator directory contains definition of what OSGi bundles to load and start and when. This should be retained and should not be deleted.
In the event it is also deleted, we can restore functioning by running a command from one level up :
.\jre\bin\java -jar .\tools\osgi-configurator.cli.jar -d .\product\enterprisemanager -b .\config\bundles-configuration.txt