Hitachi

Hitachi Application Server V10 User's Guide (For Windows® Systems)


10.3.1 Trace collection points of performance tracer

The following explains the trace collection points of performance tracer and information that can be collected.

PRF trace refers to the trace information that is output at a predetermined processing point of the Java EE server. It is a binary file that can be output by setting the PRF trace collection level.

To enable a series of processing steps to be traced, consistent keys are set and managed for a series of processing steps of each event unit. Key information is added to the trace that is output at the point (trance collection point) when trace information in the event is output. The table below lists the key information.

Table 10‒1: Key information of PRF traces

Number

Key information of PRF traces

Description

1

Root application information

Information that must be kept as a unique value in the processing sequence across multiple processes

Application Server adds root application information at the place identified as the start point of the sequence. For example, if a connection is made to Application Server from an application client, root application information is added when the application client starts. If a connection is made to Application Server from another client, such as a web browser, root application information is added when the request is received by the web server.

2

Client application information

Information that must be kept as a unique value in the processing sequence between the client and the server

Application Server adds client application information at the place identified as the start point of communications between the client and the server.

For example, the client application information is added immediately before a communication message is transmitted, such as for HTTP communications for a web service call or for RMI/IIOP communications for an EJB call.

Because root application information is output to the Web Server log file (request logs and access logs), you can check root application information by comparing the Web Server log file with the performance analysis trace file#.

#:

A file in which a PRF trace is changed to text (CSV) format.

The table below lists the trace collection points in each function layer.

Table 10‒2: Trace collection points

Number

Function layer

Event ID#

1

Web container

From 0xB100 to 0xB101

From 0xB200 to 0xB203

2

EJB container

From 0xB300 to 0xB307

From 0xBB00 to 0xBB03

3

JNDI

From 0xB400 to 0xB401

4

JTA

From 0xB500 to 0xB507

5

JDBC

From 0xB600 to 0xB665

6

JSF

From 0xB700 to 0xB70D

7

JMS

From 0xB800 to 0xB81F

8

JAX-RS

From 0xB900 to 0xB905

9

JAX-WS

From 0xBA00 to 0xBA0B

#:

PRF trace output point and position information in each process