7.7.7 Investigating the Log Using the Root Application Information
If the application API is used in a J2EE application or batch application, the character string expression of root application information of the performance analysis information can be output to the log file at any time.
The character string expression of the root application information is output to the following format (maximum 48 characters):
IP address / process ID / communication number (Example: 10.209.15.130/1234/0x0000000000000001)
If the root application information is output to a log file using an API, you compare the log file with the trace based performance analysis file to investigate.
When a new request is received in the Web container, a new root application information is assigned to the single request. The following table describes the trace points to which the new root application information is assigned.
|
Event ID (process contents) |
Process contents |
|---|---|
|
0x8236 |
When acquiring a request, when completing the request header analysis |
- #
-
If a Web server is connected, the root application information obtained by the HTTP Server is assigned. If the root application information was not issued because the HTTP Server or the PRF trace output library used by the HTTP Server failed to load, new root application information is assigned by the Web container.
Moreover, in the following trace collection point, 'IPaddress / process ID / communication number' might be output as '0.0.0. 0/0/0x0000000000000000'
-
0x8237
When data is read from Web client.
-
0x8238
When data is written to the Web client.
In the following cases the IP-address/process-ID/communication-number is output as 0.0.0. 0/0/0x0000000000000000:
-
If an HTTP request header is received
-
If an incorrect data that is not an HTTP request is received
-
If an exception occurs during processing of the request
Note that the APIs used to output the character string expression of the root application information is the getRootApInfo method of the CprfTrace class, provided in the com.hitachi.software.ejb.application.prf package.
For details on the implementation of acquiring the root application when the J2EE application or batch application is started, see the section 7.4 Implementation for collection of root application information of trace based performance analysis. For details on the APIs, see the uCosminexus Application Server API Reference Guide.