Intermittent portal startup failures due to BundleException

Issue

Intermittent portal start up failures occur when the following BundleException error is observed:

 Caused by: org.osgi.framework.BundleException: Cannot transiently start a module whose start level is not met.
at org.eclipse.osgi.container.Module.start(Module.java:413)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:428)
at org.eclipse.equinox.console.command.adapter.Activator$GOGO.start(Activator.java:89)
at org.eclipse.equinox.console.command.adapter.Activator.start(Activator.java:328)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
... 12 more

Environment

Quarterly Release
DXP 7.4

Resolution

The root cause according to the logs is:
```
Cannot transiently start a module whose start level is not met.
```
This normally means there is a dependency of different start level (custom) modules. Please refer to the properties of module.framework.*.start.level in system.properties.

For example, you should not have *-service module depending on *-web module as *-service module is dynamic.install start level (which is 10 by default), while *-web is web start level which is 15 by default.
Solution:

1. Figure out which modules cause this.
2. Remove the dependency between them.