On this page:
The GlassFish application server versions 3.x and later uses OSGi architecture. By default, OSGi containers follow a specific model for bootstrap class delegation. Classes that are not specified in the container's CLASSPATH are not delegated to the bootstrap classloader; therefore you must configure the OSGi containers for the Java Agentclasses.
For more information see GlassFish OSGi Configuration per Domain.
To ensure that the OSGi container identifies the Java Agent, specify the following package prefix:
This prefix follows the regular boot delegation model so that the Java Agent classes are visible.
If you already have existing boot delegations, add "com.singularity.*" to the existing path separated by a comma. For example:
If running Eclipse Equinox under Glassfish:
Add the following package prefix to the config.ini file:
If running Eclipse Equinox under the WebSphere Application Server Liberty profile:
Add the following line:
For more information see Getting Started with Equinox.
Add following package prefix to the sling.properties file:
For JIRA 5.1.8 and newer and Confluence 5.3 and newer:
Open the startup script (i.e., catalina.sh) for editing.
Look for the
start command block (look for "
elif [ "$1" = "start" ] ; then")
Add the following Java system property alongside the existing properties in both
Add the property to the run command block as well to instrument the application started in run mode. For example:
For Windows, use
For other OSGI-based runtime containers, add the following package prefix to the appropriate OSGi configuration.