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

Table 8-150 Details of the trace collection points in JMS Connection interface

Event ID	Number in the figure#	Trace collection point	Level
0xA60E	1	When the processing of Connection.createSession(transacted,acknowledgeMode) starts	A
0xA60F	4	When the processing of Connection.createSession(transacted,acknowledgeMode) ends	A
0xA610	1	When the processing of QueueConnection.createQueueSession(transacted,acknowledgeMode) starts	A
0xA611	4	When the processing of QueueConnection.createQueueSession(transacted,acknowledgeMode) ends	A
0xA612	1	When the processing of TopicConnection.createTopicSession(transacted,acknowledgeMode) starts	A
0xA613	4	When the processing of TopicConnection.createTopicSession(transacted,acknowledgeMode) ends	A
0xA614	5	When the processing of Connection.close() starts	A
0xA615	8	When the processing of Connection.close() ends	A
0xA616	2	Invocation by CJMSP Broker immediately before creating the session	A
0xA617	3	Invocation by CJMSP Broker just after creating the session	A
0xA618	6	Invocation by CJMSP Broker immediately before disconnection	A
0xA619	7	Invocation by CJMSP Broker just after disconnection	A

Legend:

A: Standard

#

Corresponds to the numbers in Figure 8-94.

The following figure shows the trace collection points of the JMS Connection interface.

Figure 8-94 Trace collection points of the JMS Connection interface

The following table describes the trace information that can be collected for the JMS Connection interface.

Table 8-151 Trace information that can be collected for the JMS Connection interface

Number in the figure#	Event ID	Level	Information that can be collected
			Interface name	Operation name	Option
1	0xA60E	A	Transaction	Ack mode	N
	0xA610	A
	0xA612	A
2	0xA616	A	N	N	N
3	0xA617	A	N	N	N
4	0xA60F	A	N	N	N
	0xA611	A
	0xA613	A
5	0xA614	A	N	N	N
6	0xA618	A	N	N	N
7	0xA619	A	N	N	N
8	0xA615	A	N	N	N

Legend:

A: Standard

N: Not applicable

#

Corresponds to the numbers in Figure 8-94.

Note

The event IDs 0xA618 and 0xA619 are also output when the Message-driven Bean applications are not running.

Reference note

The Acknowledgement mode is output using a numerical value. The numerical value is mapped to the types of Acknowledgement modes. The mapping is as follows:

• AUTO_ACKNOWLEDGE = 1
• CLIENT_ACKNOWLEDGE = 2
• DUPS_OK_ACKNOWLEDGE = 3
• SESSION_TRANSACTED = 0

The numerical values of the respective modes are defined in the JMS specifications.