8.7.2 Trace collection points and trace information that can be collected during request processing for updating an HTTP session (Trace of database session failover functionality)
This subsection describes the trace collection points and the trace information that can be collected during request processing for updating an HTTP session.
- Organization of this subsection
(1) Trace collection points and PRF trace collection levels
The following table describes the event IDs, trace collection points, and PRF trace collection levels.
|
Event ID |
No. in the figure#1 |
Trace acquisition points |
Level |
|---|---|---|---|
|
0x8202 |
6 |
Immediately before invoking a servlet or JSP |
A/B |
|
0x8203 |
6 |
Immediately before invoking the filter that is executed before the execution of the servlet or JSP that receives the request (filter for which the <dispatcher> tag of the <filter-mapping> tag of web.xml is omitted, or for which REQUEST is specified in the <dispatcher> tag) |
B |
|
0x8207 |
6 |
Immediately before invoking the static contents (DefaultServlet) |
B |
|
0x8219#2 |
8 |
Immediately before starting the serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8220 |
4 |
Immediately before starting the de-serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8221 |
2 |
Immediately before starting database access before the Web application processing with the database session failover functionality |
A |
|
0x8222#2 |
10 |
Immediately before starting database access after the Web application processing with the database session failover functionality |
A |
|
0x8236 |
1 |
Immediately after a request is acquired, or when the request header analysis is complete |
A |
|
0x8302 |
7 |
Immediately after the completion of processing of the servlet or JSP |
A/B |
|
0x8303 |
7 |
Immediately after the completion of processing of the filter that is executed before the execution of the servlet or JSP that receives the request (filter for which REQUEST is specified in the <dispatcher> tag of the <filter-mapping> tag of web.xml) |
B |
|
0x8307 |
7 |
Immediately after the completion of processing of the static contents (DefaultServlet) |
B |
|
0x8316 |
7 |
Immediately after the completion of processing of the filter executed during transfer to the error page is complete (filter for which ERROR is specified in the <dispatcher> tag of the <filter-mapping> tag of web.xml) |
B |
|
0x8319#2 |
9 |
Immediately after the termination of serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8320 |
5 |
Immediately after the termination of de-serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8321 |
3 |
Immediately after the termination of database access before the Web application processing with the database session failover functionality |
A |
|
0x8322#2 |
11 |
Immediately after the termination of database access after the Web application processing with the database session failover functionality |
A |
|
0x8336 |
12 |
Immediately after the completion of request processing |
A |
- Legend:
-
A: Standard
B: Advanced
A/B: Different information is collected for the Standard and Advanced levels.
- #1
-
Corresponds to the numbers in Figure 8-14.
- #2
-
Not output for requests meant for referencing the HTTP session.
The following figure shows the trace collection points.
|
|
![[Figure]](GRAPHICS/ZU075100.GIF)
(2) Trace information that can be collected
The following table describes the trace information that can be collected during request processing for updating an HTTP session.
|
No. in the figure# |
Event ID |
Level |
Information that you can acquire |
||
|---|---|---|---|---|---|
|
Interface name |
Operation name |
Optional |
|||
|
1 |
0x8236 |
A |
HTTP method |
URI |
Value for the request header name specified in the property (none if the header name is not specified) |
|
2 |
0x8221 |
A |
-- |
-- |
Number-of-session-ID-characters: session-ID-received-with-the-request |
|
3 |
0x8321 |
A |
|
-- |
|
|
4 |
0x8220 |
A |
Request URL |
Size (bytes) of the HTTP session property information before de-serialization |
Number-of-session-ID-characters: session-ID |
|
5 |
0x8320 |
A |
Request URL |
-- |
|
|
6 |
0x8202 |
A |
Class name (JSP file name when a JSP is invoked) |
-- |
-- |
|
B |
Context root name |
Number-of-session-ID-characters: session-ID: number-of-global-session-ID-characters: global-session-ID |
|||
|
0x8207 |
B |
-- |
Context root name |
Number-of-session-ID-characters: session-ID: number-of-global-session-ID-characters: global-session-ID |
|
|
0x8203 |
B |
Class name |
Context root name |
Number-of-session-ID-characters: session-ID: number-of-global-session-ID-characters: global-session-ID |
|
|
7 |
0x8302 |
A |
Class name (JSP file name when a JSP is invoked) |
-- |
|
|
B |
Context root name |
|
|||
|
0x8307 |
B |
-- |
Context root name |
|
|
|
0x8303 |
B |
Class name |
Context root name |
|
|
|
0x8316 |
B |
Class name |
Context root name |
|
|
|
8 |
0x8219 |
A |
Request URL |
-- |
Number-of-session-ID-characters: session-ID |
|
9 |
0x8319 |
A |
Request URL |
Size (bytes) of the HTTP session property information after serialization |
|
|
10 |
0x8222 |
A |
-- |
-- |
Number-of-session-ID-characters: session-ID-of-HTTP-session |
|
11 |
0x8322 |
A |
|
-- |
|
|
12 |
0x8336 |
A |
HTTP method |
URI |
Entrance-time status-code |
- Legend:
-
A: Standard
B: Advanced
--: Not applicable
- #
-
Corresponds to the numbers in Figure 8-14.