OSGi bundles or plugins may fail to resolve or start, affecting application startup. The following errors may be displayed in the terminal output or application error logs:
java.lang.NoClassDefFoundError:
com/manageengine/apminsight/agent/JavaAgent
OSGi bundles run in isolated class loaders and may not be able to access JVM-internal packages or externally injected classes, such as those provided by monitoring agents, unless the required packages are explicitly boot-delegated to the parent class loader.
Add the APM Insight Java agent package, com.manageengine.*, to the existing boot delegation Java property.
For example:
-Dorg.osgi.framework.bootdelegation=com.sun.*,com.manageengine.*

The platform-specific properties and configuration locations are listed in the source document.
Platform | Property | Configuration location |
Liferay DXP | module.framework.properties.org.osgi.framework.bootdelegation | portal-ext.properties |
Atlassian Jira/Confluence | -Datlassian.org.osgi.framework.bootdelegation.extra | setenv.sh |
Adobe Experience Manager (Sling) | -Dorg.osgi.framework.bootdelegation | sling.properties |
Other OSGi platforms/bundled applications | -Dorg.osgi.framework.bootdelegation | Startup script, existing JAVA_OPTS, or another location where Java properties are maintained |
If an OSGi-based application fails to start with a NoClassDefFoundError or ClassNotFoundException error message for an APM Insight Java agent class, verify that com.manageengine.* has been added to the platform’s existing boot delegation configuration.