The following table describes the events IDs, trace collection points, and PRF trace collection levels when an in-process HTTP server is used.

Table 8-10 Details of trace collection points in an in-process HTTP server

Event ID	No. in the figure#1	Trace acquisition points	Level
0x8202#2	5	Immediately before a servlet or JSP is invoked	A/B
0x8203	4	Immediately before the filter that is executed before the execution of the servlet or JSP that receives the request is invoked (when the [[dispatcher]] tag of the [[filter-mapping]] tag of web.xml is omitted or when a filter for which REQUEST is specified in the [[dispatcher]] tag is invoked)	B
0x8206	6	Immediately before a servlet or JSP is invoked via RequestDispatcher	B
0x8207	5	Immediately before the static contents are invoked	B
0x8211	3	Immediately after acquiring a request/completing the request header analysis	A/B
0x8212	1	Immediately before data reading from the Web client starts	B
0x8213	8	Immediately before data writing into the Web client starts	B
0x8302	10	Immediately after the completion of processing of the servlet or JSP	A
0x8303	11	Immediately after the completion of processing of the filter that is executed before the execution of the servlet or JSP that receives the request (when the processing of the filter for which REQUEST is specified in the [[dispatcher]] tag of the [[filter-mapping]] tag of web.xml is complete)	B
0x8306	7	Immediately after the completion of processing of the servlet or JSP via RequestDispatcher	B
0x8307	10	Immediately after completion of processing of static contents (DefaultServlet)	B
0x8311	12	Immediately after the completion of request processing	A/B
0x8312	2	Immediately after the completion of data reading from the Web client	B
0x8313	9	Immediately after the completion of data writing into the Web client	B

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-11.

#2

If JSP compilation is required, the trace is collected after the JSP compilation is executed.

The following figure shows the trace collection points when an in-process HTTP server is used.

Figure 8-11 Trace collection points of an in-process HTTP server

Because the request information is received from the client more than once at the points 1 and 2, the trace information is also output more than once.

Because the response information is sent to the client more than once at the points 8 and 9, the trace information is also output more than once.

Even when a request for the request body information, and a response are sent from the filter, the trace for points 2 or 8, and points 8 and 9 is output.