7.7.4 Investigating the Life Cycle of a Session
This subsection describes how to investigate the life cycle of a session using a trace based performance analysis.
You can investigate the life cycle of a session by using the trace (Session trace) that is output when the PRF trace collection level is set as details.
You can investigate session trace information by using the session ID in the output trace based performance analysis file as a key.
The session ID is output to the option area of the event, output as the session trace information in the following format:
Number of session characters: Session ID
For example, if there is a session ID called as abc123, in the option area 6:abc123 is output. When the session ID is a blank character, 0: is output as the number of session characters. When the session ID cannot be acquired, nothing is output.
The following figure gives an example of trace based performance analysis file in which the session trace information is output. In this example, the trace information of a request to generate a session, a request to use the session, and a request to destroy the session are output in the validity period of one session. Also, a request to generate a session, a request to use the session, and a request to destroy the session are shown separately. In reality, the trace information in these three examples is output one after another. In these windows, all items are related to the session trace.
|
|
![[Figure]](GRAPHICS/ZU060800.GIF)
-
In the ASCII example of the 0x8208 event, the generated session ID is output. 1800 in the option column indicate the session validity period.
The items that you can confirm in this trace file are described here.
- Confirming the validity period of the session
-
When generating a session, the 0x8208 event is output. When destroying a session, the 0x8209 event is output. You can confirm the validity range of the session from the date and time of these acquisitions. Also, in the case of the 0x8208 event, you can even confirm the validity period (seconds) of the session generated from the operation name.
The same ID is output to the event 0x8209 of the request to destroy the session until the session is destroyed. You can confirm the date and time of generating the session that is destroyed from the operation name.