uCosminexus Application Server, Maintenance and Migration Guide

[Contents][Glossary][Index][Back][Next]

8.25.1 Trace collection points in the processing between JSF and Web container and the trace information that can be collected

Organization of this subsection
(1) Trace collection points when a Web application starts and the trace information that can be collected
(2) Trace collection points when a Web application stops and the trace information that can be collected

(1) Trace collection points when a Web application starts and the trace information that can be collected

(a) Trace collection points and the PRF trace collection levels when a Web application starts

The following table describes the event IDs, trace collection points, and PRF trace collection levels.15,15,55,15

Table 8-165 Details of the trace collection points when a Web application starts

Event ID No. in the figure# Trace collection points Level
0xAF00 1 Immediately before the JSF initialization starts during Web application startup A
0xAF01 2 Immediately after the JSF initialization completes during
Web application startup		 A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-106.

The following figure shows the trace collection points when a Web application starts.

Figure 8-106 Trace collection points when a Web application starts

[Figure]

(b) Trace information that can be collected when a Web application starts

The following table describes the trace information that can be collected when a Web application starts.

Table 8-166 Trace information that can be collected when a Web application starts

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF00 A #2 -- --
2 0xAF01 A #3 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-106.

#2
The context root name of the application is output.

#3
If the application has already been initialized, already-been-initialized is output.
For the Web applications that are not JSF applications, the initialization processing is immediately terminated, and No-FacesServlet-Found-In-web.xml is output.

(2) Trace collection points when a Web application stops and the trace information that can be collected

(a) Trace collection points and PRF trace collection levels when a Web application stops

The following table describes the event IDs, trace collection points, and PRF trace collection levels.

Table 8-167 Details of the trace collection points when a Web application stops

Event ID No. in the figure# Trace collection points Level
0xAF02 1 Immediately before the JSF termination starts during the termination of a Web application A
0xAF03 2 Immediately after the JSF termination completes during the termination of a Web application A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-107.

The following figure shows the trace collection points when a Web application stops.

Figure 8-107 Trace collection points when a Web application stops

[Figure]

(b) Trace information that can be collected when a Web application stops

The following table describes the trace information that can be collected when a Web application stops.

Table 8-168 Trace information that can be collected when a Web application stops

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF02 A #2 -- --
2 0xAF03 A #3 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-107.

#2
The context root name of the application is output.

#3
If the application has not been initialized, not-been-initialized is output.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.