Click on a probe to display the configuration panel. The following common configuration options are available for each probe:
This option is not available for the "Servlets" probe.
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.
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". In the text field after the "Retain request parameters" radio button, a comma-separated list of such parameters can be specified.
However, the structure of the URLs may be more complex than that. Maybe you want to discard parts of the
request path or conditionally retain request parameters. In that case, you can use the "Resolve with script"
option and define a script that returns the string defining the
URL displayed by JProfiler. The script is passed two parameters: uri
for the request path and
queryString
for the query parameters. Just returning uri
would correspond to
the default "Request path only" setting.