3.4.11 Details of the tuning details file

This subsection describes the file name, output format, and upper-limit of the file size of the tuning details file.

Organization of this subsection
(1) File name (tuning details file)
(2) Output format (tuning details file)
(3) Upper-limit value of the total file size

(1) File name (tuning details file)

csmjaxp_ppxml_{character string indicating the Pre-Parse XML document}_{character string indicating the Pre-Parse XML document}_{serial number}.txt

Character string indicating the Pre-Parse XML document
Indicates the character string obtained from the end part of the absolute path of Pre-Parse XML document and excluding the part after the last period (.).
Example: When the absolute path of the Pre-Parse XML document is D:\home\xml\training\tr1.xml
The character string indicating the Pre-Parse XML document will be tr1.
Character string indicating the XML document for parsing
Indicates the character string obtained from the end part of the system identifier of XML document for parsing and excluding the part after the last period (.).
Example: When the system ID of the XML document for parsing is file:/home/xml/data/novelA.xml
The character string indicating the XML document for parsing will be novelA.
Serial number
Serial number from 00 to 99. This number increases with each parsing.
Note that this number will be reset to 00 when the J2EE server or Web container is restarted. After 99 it would be reset to 00.

(2) Output format (tuning details file)

Output lineOutput contents
First lineHeader indicating the tuning details file

Cosminexus XML Processor Fast Parse Function Tuning Detail Information

Second lineDate and time when the tuning details file was created
Third lineFile name of the Pre-Parse XML document
Fourth lineSystem identifier of the XML document for parsing
If the system identifier is not set up, null will be output.
Fifth lineHeader indicating the start of the matching information

Matching Information start

Sixth line and thereafterMatching information (history of the matching process)
When the matching process is successful
o:{element or attribute for which the matching process was executed}#
When the matching process fails
x: expected {pattern where matching was tried}# but {pattern that appears in the XML document for parsing}#
Second from the last lineFooter indicating the end of the matching information

Matching Information end

Last lineSuccess rate of the matching process
Success frequency [Figure] matching process execution frequency [Figure] 100 (%)
However, if the matching process is not executed even once, 0.0% will be output
#
Only a part of the element or attribute is output. The characters before and after the element or attribute are also output. For a specific example, see the output example:

Output example
[Figure]

(3) Upper-limit value of the total file size

32 MB#

#
If the total file size of the output tuning details files exceeds 32 MB, no more tuning detail files will be generated thereafter.
For example, if the tuning detail files are generated in the following order of 1 to 5, and if the total file size of 1 to 4 files while the 4th file is being generated becomes 40 MB, which is greater than 32 MB, the fifth file will not be generated.
  1. csmjaxp_ppxml_trl_novelistA_00.txt (10MB)
  2. csmjaxp_ppxml_trl_novelistB_00.txt (10MB)
  3. csmjaxp_ppxml_trl_novelistC_00.txt (10MB)
  4. csmjaxp_ppxml_trl_novelistD_00.txt (10MB)
  5. csmjaxp_ppxml_trl_novelistE_00.txt (10MB)
Note that the upper-limit value of the total file size can be changed by the following system property.
System property name
com.cosminexus.jaxp.preparsedxml.tuning.detailfile_totalmaxsize
Value
Specify an integer value as 0 or more. The unit is MB.
If this property is not set up, and if a value out of range is specified, 32 will be set up.