7.6.2 Logs for application rewriting

The user-extended trace based performance analysis uses the instrumentation functionality and rewrites the application classes when the class is loaded, in order to output the trace based performance analysis. The following table describes the logs output at this time.

Table 7‒10: Logs for application rewriting
Output format	Output contents	Explanation
`[UPR`^#1`]<DATE>BCI process failed.<class=CLASS>`	`DATE`^#2 The date and time at which an attempt to rewrite failed. `CLASS` The fully qualified class name for which rewriting failed.	An attempt to rewrite the class specified in the configuration file for the user-extended trace based performance analysis failed.
`[UPR`^#1`]<DATE>BCI process finished successfully.<class=CLASS>`	`DATE`^#2 The date and time at which rewriting was successful. `CLASS` The fully qualified class name for which rewriting was successful.	The class specified in the configuration file for the user-extended trace based performance analysis was successfully rewritten. Note that this log is output when `true` is specified in the `jvm.userprf.Trace` property.
`[UPR`^#1`]<DATE>BCI count exceeded a limit.`	`DATE`^#2 The date and time at which the rewriting count exceeded the upper limit.	An attempt was made to rewrite the methods to be traced, exceeding the number specified in the `jvm.userprf.Limit` property. Take one of the following actions: Reduce the number of target methods of the user-extended trace based performance analysis. Increase the value specified in the `jvm.userprf.Limit` property. Note that this log is output when the value specified in the `jvm.userprf.Limit` property is exceeded for the first time.

#1: An identifier indicating that the log was output by the user-extended trace based performance analysis.
#2: Output in the same format as the extended verbosegc information.

To Page Top