The ResultRetrieve ARM statistic can be correlated to some original request using the ARM transactions only if XPARENT-1 and XPARENT-2 have a common ancestor transaction. The invocation of request, and result retrieve occur on different threads
Event monitoring for SCA components includes
the event points that are shown in black , while the event points
shown in blue
are used only to calculate and fire PMI/ARM statistics.
In the table and diagram below, the "current" ARM transaction (denoted as X1) is created when the calling service component was invoked for the first time. If the caller is not a service component, the current arm transaction will be used, or a new one will be created. If it is not the starting transaction it will have a parent. This is represented in the following table and diagram with the notation Xn.Xn+1. These are used to show the transaction lineage. Every SCA invocation starts a new transaction, which is parented by the current transaction of the caller. You can create new transactions and you can access the current transaction, but this will not modify the SCA transaction lineage.
Type | Statistics | Formula | ARM Transaction |
---|---|---|---|
Common | TotalResponseTime | t3 - t0 | X0.X1 |
RequestDeliveryTime | t'0 - t0 | X1.X2 | |
ResponseDeliveryTime | N/A | N/A | |
GoodRequests | CountEXIT | X1.X2 | |
BadRequests | CountFAILURE | ||
ResponseTime | See specific diagrams | ||
Reference A | GoodReferenceRequest | CountEXIT | X1.X2 |
BadReferenceRequests | CountFAILURE | ||
ReferenceResponseTime | t1 - t0 |
Type | Statistics | Formula | ARM Transaction |
---|---|---|---|
Reference B | GoodRetrieveResult | CountEXIT | X'0.X'1 |
BadRetrieveResult | CountFAILURE | ||
RetrieveResultResponseTime | Σ t3 - t2 | ||
RetrieveResultWaitTime | Σ timeout |