The following options are available:
- Maximum recorded number of payloads per call stack
Probes can publish information into the
For each call stack and payload type, JProfiler keeps track of
the invocation count and total execution times for each thread status. To avoid excessive memory consumption,
there is a cap on the number of different retained payload names. If the maximum
number is exceeded, the oldest payload is merged into an "[earlier calls]" node. By default,
this maximum value is set to 50. If you require more detail, you can increase the value in the text field
- Record exact payload call stacks in sampling mode
If sampling is enabled, JProfiler still records the exact call stack of payloads in order
to generate useful back traces in the probe hot spots views.
If you are not interested in these back traces, you can deselect this option in order
to reduce overhead.
- Maximum number of recorded events
Probes can record single events and show them in the
probe events view.
To avoid excessive memory consumption, there is a cap on the maximum number of retained events. If the maximum
number is exceeded, the oldest events are discarded. By default,
this maximum value is set to 5000 per thread. If you require more history, you can increase the value in the text field
- Detect Java EE components
JProfiler can detect the following Java EE component types:
The corresponding methods have a separate icon in the call tree. For JSPs, the name of the
JSP source file is displayed instead of the generated class and for EJBs the name of the interface
is displayed instead of the generated stub or proxy classes. In the "method" and the "class" aggregation levels,
the real class names are displayed in square brackets, too.
Based on this component information, JProfiler offers the Java EE components aggregation level
in all views with an aggregation level selector. If you would like to disable Java EE component
detection, you can deselect the checkbox labeled Detect Java EE components.
- Show request URLs without a recorded call stack
The servlet probe splits the call tree for each recorded request URL. Request URLs that
do not have an associated call stack are not shown by default. To display these request URLs
at the top level of the call tree you can select this option.