This option is not available for the "Class Loaders" probe, where single events are always recorded.
This option is not available for the "Servlets" and "Class Loaders" probe.
When you select the option to split the servlet request with scripts, you can click
on the "Edit scripts"
button to set up one or more scripts that determine how the call tree is split. The
[Add] button shows you a number
of pre-defined templates that are useful starting points. For example, the "Split
by request URI" script
has the same effect as the default mode for URL splitting.
In reality, there may be certain request parameters that should be retained for URL splitting, such as parameters that do not identify user input, but determine the type of the request. For example, you may have a dispatcher servlet and a parameter "controller" that determines the type of the request. In that case, you would probably like to retain the parameter "controller" and change the script to
servletRequest.getRequestURI() + "/controller=" + servletRequest.getParameter("controller")
The script is passed two parameters, first an instance of com.jprofiler.api.agent.ScriptContext that allows you to store data across subsequent requests, and - more importantly - an instance of javax.servlet.http.HttpServletRequest that gives you access to all information regarding the intercepted servlet request.
When you add a second script, a second splitting level is introduced. For example, the first script could split by session ID, and the second script by request URI. In that way, you could look at the activity generated by a specific user in isolation. At the top, you could add a third script that splits by the context path. This would enable you to analyze multiple deployed web applications separately.
You can temporarily disable scripts with the "Disable selected" action in the tool bar or in the context menu. This allows you to experiment with multiple scripts without deleting and re-entering the script entries.
All nodes in the call tree that are created by URL splitting are prefixed with "HTTP:".
toString()
value of the destination
returned by javax.jms.Message#getJMSDestination()
.
With the "message resolver script" you can display customized information on your
messages. The
script receives a parameter "message" which is of type
java.lang.Object
. This is because the JMS classes may not be available in the profiled JVM,
so the JMS probe cannot depend on them. You can cast the message to a subtype of javax.jms.Message,
extract the relevant information and return a string that will be displayed in the
JProfiler GUI. That string
is the basis for the hot spots calculation in the hot spots view.
For server calls, the call tree is split similar to the servlet probe. There are two splitting modes, one that groups all calls from each IP address, and another that also splits for each port. The latter option is useful if you have multiple clients on a single remote machine and you want to separately see those calls in the call tree.