Hitachi

uCosminexus Application Server Maintenance and Migration Guide


8.11.6 Trace collection points and trace information that can be collected when work management is used

This subsection describes the trace collection points and the trace information that can be collected when work management is used in a resource adapter conforming to Connector1.5.

Note that if you are using a resource adapter other than the product resource adapter, new numbers will be allotted to the root AP information when 0x8B86 is output. If the <resourceadapter>-<resourceadapter-class> value of DD (ra.xml) starts with "com.hitachi" or "com.cosminexus", the resource adapter will be considered as a product resource adapter.

The root AP information set at the entrance of MDB container is treated as the root AP information of Work, if you invoke Message-driven Bean from Work. Individual Message-driven Bean processing is distinguished by the thread ID.

Organization of this subsection

(1) Trace get point and the PRF trace get level

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

Table 8‒87: Details of trace collection points in a DB Connector and JCA container (when work management is used)

Event ID

No. in the figure#

Trace acquisition points

Level

0x8B86

1

Immediately after invoking a method of javax.resource.spi.work.WorkManager

A

0x8B87

6, 9, 14

Immediately before the return of the method of javax.resource.spi.work.WorkManager

A

0x8B88

2, 4, 7, 12

Immediately before invoking a method of javax.resource.spi.work.WorkListener

B

0x8B89

3, 5, 8, 13

Immediately after the return of the method of javax.resource.spi.work.WorkListener

B

0x8B8A

10

Immediately before invoking a method of javax.resource.spi.work.Work

A

0x8B8B

11

Immediately after the return of the method of javax.resource.spi.work.Work

A

Legend:

A: Standard

B: Advanced

#

Corresponds to the numbers in Figure 8-50 through Figure 8-52.

The following figure shows the trace collection points.

Figure 8‒50: Details of trace collection points in a DB Connector and JCA container (when scheduleWork() is invoked)

[Figure]

Figure 8‒51: Details of trace collection points in a DB Connector and JCA container (when startWork() is invoked)

[Figure]

Figure 8‒52: Details of trace collection points in a DB Connector and JCA container (when doWork() is invoked)

[Figure]

(2) Trace information that can be collected

The following table describes the trace information that can be collected.

Table 8‒88: Details of trace collection points in a DB Connector and JCA container (when work management is used)

No. in the figure#1

Event ID

Level

Information that you can acquire

Interface name

Operation name

Optional

1

0x8B86

A

Work class name

Method name

Display name of the resource adapter

2

0x8B88

B

Work class name

Method name

Display name of the resource adapter#2

3

0x8B89

B

Work class name

Method name

  • When normal:

    Entrance-time

  • For an exception:

    Entrance-time exception-name

4

0x8B88

B

Work class name

Method name

Display name of the resource adapter#2

5

0x8B89

B

Work class name

Method name

  • When normal:

    Entrance-time

  • For an exception:

    Entrance-time exception-name

6

0x8B87

A

Work class name

Method name

7

0x8B88

B

Work class name

Method name

Display name of the resource adapter#2

8

0x8B89

B

Work class name

Method name

  • When normal:

    Entrance-time

  • For an exception:

    Entrance-time exception-name

9

0x8B87

A

Work class name

Method name

10

0x8B8A

A

Work class name

Method name

Display name of the resource adapter#2

11

0x8B8B

A

Work class name

Method name

  • When normal:

    Entrance-time

  • For an exception:

    Entrance-time exception-name

12

0x8B88

B

Work class name

Method name

Display name of the resource adapter#2

13

0x8B89

B

Work class name

Method name

  • When normal:

    Entrance-time

  • For an exception:

    Entrance-time exception-name

14

0x8B87

A

Work class name

Method name

Legend:

A: Standard

B: Advanced

#1

Corresponds to the numbers from Figure 8-50 to Figure 8-52.

#2

In the case of a resource adapter included in the application, application-name: display-name-of-resource-adapter is displayed.