Page Comparison

...

This is necessary to assure the proper classloader creates the agent classes.

Configuration via editor:

Edit the config\domain.xml file of the domain and add three four lines to the java-config element:

<jvm-options>-Xbootclasspath/p:${com.sun.aas.instanceRoot}/lib/ext/inspectit-agent.jar</jvm-options>
<jvm-options>-javaagent:${com.sun.aas.instanceRoot}/lib/ext/inspectit-agent.jar</jvm-options>

<jvm-options>-Dinspectit.repository=[REPOSITORY_IP]:[REPOSITORY_PORT]</jvm-options>
<jvm-options>-Dinspectit.agent.name=[AGENT_DISPLAY_NAME]</jvm-options>

Configuration via asadmin configuration console:

Run the following commands in the asadmin configuration console:

create-jvm-options "-Xbootclasspath/p\:${com.sun.aas.instanceRoot}/lib/ext/inspectit-agent.jar"


create-jvm-options "-javaagent\:${com.sun.aas.instanceRoot}/lib/ext/inspectit-agent.jar"


create-jvm-options "-Dinspectit.repository=[REPOSITORY_IP]\:[REPOSITORY_PORT]"


create-jvm-options -Dinspectit.agent.name=[AGENT_DISPLAY_NAME]

Configuration via administration console:

Open the administration console (typically http://localhost:4848/ ), log-in to the server and make sure you are in the right domain.

...

Then select Configuration>JVM Settings and switch to the tab JVM Options. Here add the three JVM Options like above with the proper paths inserted.

Press save.

In both cases you have to restart the server for the changes to take effect. If you have configured your agent properly, you should see a message like

...

...

If you use GlassFish version 3.1.2+ and 4+ you should configure the OSCi Containers for our Javaagent classes. Not doing so might result in following kind of exceptions:

...