15.10.1 Trace collection points and trace information that can be collected during request processing for creating an HTTP session (Trace of the database session failover functionality)
This section describes the trace collection points and the trace information that can be collected during request processing for creating 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# |
Trace acquisition points |
Level |
|---|---|---|---|
|
0x8200 |
1 |
Immediately after the acquisition of a request, or after the completion of the request header analysis (via the Web server) |
A/B |
|
0x8202 |
2 |
Immediately before invoking a servlet or JSP |
A/B |
|
0x8203 |
2 |
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 |
2 |
Immediately before invoking the static contents (DefaultServlet) |
B |
|
0x8211 |
1 |
Immediately after the acquisition of a request, or after the completion of the request header analysis (via the in-process HTTP server) |
A/B |
|
0x8219 |
6 |
Immediately before starting the serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8222 |
8 |
Immediately before starting database access after the Web application processing with the database session failover functionality |
A |
|
0x8223 |
3 |
Immediately before starting database access during the creation of the HTTP session with the database session failover functionality |
A |
|
0x8300 |
10 |
Immediately after the completion of request processing (via the Web server) |
A/B |
|
0x8302 |
5 |
Immediately after the completion of processing of the servlet or JSP |
A/B |
|
0x8303 |
5 |
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 |
5 |
Immediately after the completion of processing of the static contents (DefaultServlet) |
B |
|
0x8311 |
10 |
Immediately after the completion of request processing (via the in-process HTTP server) |
A/B |
|
0x8316 |
5 |
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 |
7 |
Immediately after the termination of serialization of the HTTP session property information with the database session failover functionality |
A |
|
0x8322 |
9 |
Immediately after the termination of database access after the Web application processing with the database session failover functionality |
A |
|
0x8323 |
4 |
Immediately after the termination of database access during the creation of the HTTP session with the database session failover functionality |
A |
- Legend:
-
A: Standard
B: Advanced
A/B: Different information is collected for the Standard and Advanced levels.
- #
-
Corresponds to the numbers in Figure 15-12.
The following figure shows the trace collection points.
|
|
![[Figure]](GRAPHICS/ZU075000.GIF)
(2) Trace information that can be collected
The following table describes the trace information that can be collected during request processing for creating an HTTP session.
|
No. in the figure# |
Event ID |
Level |
Information that you can acquire |
||
|---|---|---|---|---|---|
|
Interface name |
Operation name |
Optional |
|||
|
1 |
0x8200 |
A |
HTTP method |
URI |
-- |
|
B |
Number-of-session-ID-characters: session-ID: collection-method |
||||
|
0x8211 |
A |
HTTP method |
URI |
-- |
|
|
B |
Number-of-session-ID-characters: session-ID: collection-method |
||||
|
2 |
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 |
|
|
3 |
0x8223 |
A |
-- |
-- |
-- |
|
4 |
0x8323 |
A |
|
-- |
|
|
5 |
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 |
|
|
|
6 |
0x8219 |
A |
Request URL |
-- |
Number-of-session-ID-characters: session-ID |
|
7 |
0x8319 |
A |
Request URL |
Size (bytes) of the HTTP session property information after serialization |
|
|
8 |
0x8222 |
A |
-- |
-- |
Number-of-session-ID-characters: session-ID-of-HTTP-session |
|
9 |
0x8322 |
A |
|
-- |
|
|
10 |
0x8300 |
A |
HTTP method |
URI |
|
|
B |
|
||||
|
0x8311 |
A |
HTTP method |
URI |
Entrance-time status-code |
|
|
B |
Entrance-time status-code number-of-session-ID-characters: session-ID: number-of-global-session-ID-characters: global-session-ID |
||||
- Legend:
-
A: Standard
B: Advanced
--: Not applicable
- #
-
Corresponds to the numbers in Figure 15-12.