Introduction

Installation


Interface

Installation

Installation should be very easy. For any JVM you wish to profile, use the following syntax:

<path to java home/bin/java> -javaagent:<path to agent>/discotek.execution-profiler-agent-1.2.0.jar="<path to configuration properties file>" 

Here is an example of how the Execution Profiler could be used to understand how WebLogic handles Servlets and JSPs.

-javaagent:/agents/discotek.execution-profiler-agent-1.2.0.jar=/profiler/execution-profiler.properties" 

The configuration properties file is a standard Java properties file containing name=value pairs on separate lines. It supports the following properties:

NameValue
classes A regular expression describing the fully qualified classes you want to be profiled. There can be multiple classes entries in the properties file.
tracing-enabled true or false. Allows you to control profiling on JVM start up. You can also use the GUI to turn it on or off once the JVM has started.
show-gui true or false. If set to true, the GUI will be launched at JVM start up.

Here is a sample properties file you might use for figuring out how JSPs or JSF HTTP requests are handled:

classes=.*servlet.*
classes=.*Servlet.*
classes=.*web.*
classes=.*jsp.*
classes=.*http.*
classes=.*Http.*
classes=.*face.*
tracing-enabled=true
show-gui=true

READ THIS!!! Please be aware that if you deploy this or other agents to 7u65 or 8u11 or newer, you will may get java.lang.VerifyError issues. The cause is related to Stack Map Frames and is discussed here and here. This may be fixed in a future version of Execution Profiler, but until then you will likely have to use the -noverifier JVM parameter. As Execution Profiler should never be deployed to a production environment, this inconvenience shouldn't pose a significant problem.


Introduction

Installation


Interface