![[Contents]](FIGURE/CONTENT.GIF)
uCosminexus Application Server, Maintenance and Migration Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
This section describes the trace collection points and the trace information that can be collected during request processing for creating an HTTP session.
The following table describes the event IDs, trace collection points, and PRF trace collection levels.
Table 8-26 Details of the trace collection points during request processing for creating an HTTP session (EADs session failover functionality)
| Event ID | No. in the figure# | Trace collection points | Level |
|---|---|---|---|
| 0x8200 | 1 | Obtaining a request or analyzing the request header (via a Web server) | A/B |
| 0x8202 | 2 | Immediately before a servlet/JSP is invoked | A/B |
| 0x8203 | 2 | Immediately before invoking the filter executed before executing the servlet/JSP that receives the request (filter for which the <dispatcher> tag is omitted in the <filter-mapping> tag of web.xml, or a filter specifying REQUEST in the <dispatcher> tag) | B |
| 0x8207 | 2 | Immediately before invoking the static contents (DefaultServlet) | B |
| 0x8211 | 1 | Immediately after the process of obtaining a request or analyzing a request header is complete (via an in-process HTTP server) | A/B |
| 0x8227 | 6 | Immediately before the EADs session failover functionality starts serializing the HTTP session attribute information | A |
| 0x8230 | 8 | Immediately before the EADs session failover functionality starts accessing the EADs after processing a Web application | A |
| 0x8231 | 3 | Immediately before the EADs session failover functionality starts accessing the EADs for creating an HTTP session | A |
| 0x8300 | 10 | Immediately after the processing is completed (via a Web server) | A/B |
| 0x8302 | 5 | Immediately after the servlet/JSP processing is complete | A/B |
| 0x8303 | 5 | Immediately after completing the processing of the filter executed before executing the servlet/JSP that receives the request (filter specifying REQUEST in the <dispatcher> tag of the <filter-mapping> tag in web.xml) | B |
| 0x8307 | 5 | Immediately after the processing of the static contents is complete (DefaultServlet) | B |
| 0x8311 | 10 | Immediately after the processing of a request is complete (via an in-process HTTP server) |
A/B |
| 0x8316 | 5 | Immediately after completing the processing of the filter executed for transmission to the error page (filter specifying ERROR in the <dispatcher> tag of the <filter-mapping> tag in web.xml) | B |
| 0x8327 | 7 | Immediately after the EADs session failover functionality finishes serializing the HTTP session attribute information | A |
| 0x8330 | 9 | Immediately after the EADs session failover functionality finishes accessing the EADs after processing the Web application | A |
| 0x8331 | 4 | Immediately after the EADs session failover functionality finishes accessing the EADs for creating an HTTP session | A |
The following figure shows the trace collection points.
Figure 8-19 Trace collection points during request processing for creating an HTTP session (EADs session failover functionality)
![[Figure]](FIGURE/ZU081800.GIF)
The following table describes the trace information that can be collected during request processing for creating an HTTP session.
Table 8-27 Trace information that can be collected during request processing for creating an HTTP session (EADs session failover functionality)
| No. in the figure# | Event ID | Level | Information that can be collected | ||
|---|---|---|---|---|---|
| Interface name | Operation name | Option | |||
| 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 | 0x8231 | A | -- | -- | -- |
| 4 | 0x8331 | 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 | 0x8227 | A | Request URL | -- | number-of-session-ID-characters: session-ID |
| 7 | 0x8327 | A | Request URL | Size of the HTTP session attribute information after serialization (bytes) |
|
| 8 | 0x8230 | A | -- | -- | number-of-session-ID-characters:session-ID-of-HTTP-session |
| 9 | 0x8330 | 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 | ||||
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.