The following table describes the logs output when the configuration file for the user-extended trace based performance analysis is read during the user-extended trace based performance analysis.

Table 7-9 Logs output the configuration file for the user-extended trace based performance analysis is read

Output format	Output contents	Explanation
[UPR#1]<DATE>Setting file not found.<file=FILEPATH>	DATE#2 The date and time at which an attempt to read the configuration file for the user-extended trace based performance analysis failed. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis that could not be read.	The default configuration file, or the configuration file for the user-extended trace based performance analysis specified in the jvm.userprf.File property does not exist.
[UPR#1]<DATE>Failed to open setting file.<file=FILEPATH>	DATE#2 The date and time at which an attempt to read the configuration file for the user-extended trace based performance analysis failed. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis that could not be read.	The configuration file for the user-extended trace based performance analysis cannot be opened or read.
[UPR#1]<DATE>Failed to parse setting file.<file=FILEPATH><line=LINE>	DATE#2 The date and time at which an error was detected in the configuration file for the user-extended trace based performance analysis. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis. LINE The line number in the configuration file for the user-extended trace based performance analysis.	There is a description format error in the contents of the configuration file for the user-extended trace based performance.
[UPR#1]<DATE>Event ID is invalid value.<file=FILEPATH><eventID=EventID>	DATE#2 The date and time at which an error was detected in the configuration file for the user-extended trace based performance analysis. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis. EventID: The event ID specified in the user-extended trace based performance analysis configuration file.	The event ID of the configuration file for the user-extended trace based performance analysis is outside the range of valid values.
[UPR#1]<DATE>No valid settings in setting file.<file=FILEPATH>	DATE#2 The date and time at which invalid settings were detected in the configuration file for the user-extended trace based performance analysis. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis.	The settings in the configuration file for the user-extended trace based performance analysis are invalid.
[UPR#1]<DATE>User Extended PRF started successfully.<file=FILEPATH>	DATE#2 The date and time at which the reading of the configuration file for the user-extended trace based performance analysis was successful. FILEPATH The absolute file path of the configuration file for the user-extended trace based performance analysis that was read properly.	The user-extended trace based performance analysis configuration file is read correctly, and the user-extended trace based performance analysis is now valid.

#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.

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.