| Date/Time | Process Id/Thread Id/Virtual Thread Id | "Invoke on" means that a network request has been received and diiop is beginning to work on it.
"Return on" means that the request processing is done.
The amount of time between "Invoke on" and "Return on" does not include time spent receiving and sending network data. | The object id that is the target of the network request. The most significant part of this id is the first number which indicates the object type.
The rest of the object id is used to locate and validate an object before attemping any operations on it. In Corba terms, this is the reference data of the object.
The basic idea behing showing the object ids is to uniquely identify an object and to follow what operations it is performing.
The note ids/unids are not available. I'll see about getting them included.
Here is the list of object types:
1 ACL
2 ACLENTRY
3 AGENT
4 BASE
5 DATABASE
6 DATE
7 DIRECTORY
8 DOCCOLL
9 DOCUMENT
10 EMBEDDED
11 FORM
12 ITEM
13 ITEM2
14 LOG
15 NEWS
16 OBJSRV
17 OUTLINE
18 OUTLINEENTRY
19 REPLICATION
20 RTITEM
21 SESSION
22 VECOLL
23 VIEW
24 VIEWENTRY
25 VIEWNAV
26 MIMEENT | This identifies the session that owns the object that is the target of the request. | The name of the operation that is being performed. This name comes directly from the idl. |