Using Tsam Accounting In Tsam Log Generated The WTIME Is Always Set To 0 When No LMS Running
(Doc ID 2103558.1)
Last updated on SEPTEMBER 14, 2023
Applies to:
Oracle Tuxedo - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Enabling tsam logs '-a /tmp/testWtime/domains/simpapp/tsam$ALL' in server CLOPT.
The WTIME returned is always set to 0 when a Tuxedo service.
Create a basic test where messages stay in queue several secs, call a Tuxedo service that sleep 2 secs, only 2 instances running and 8 Tuxedo clients calling LTOUPPER (with a sleep) or TOUPPER(without a sleep), then report generated via TSAM Plus Accounting and Chargeback (accrpt utility) looks like:
#DID LMID GRPID GRPNAME SID PID PNAME SVC GID UID CLIENT STIME ETIME TIME SYSTIME USRTIME ERRNO URCODE SIZE WTIME
SITEA 1 GRPAPP 10 simpserv TOUPPER 1454599748 1454599748 0 0 0 0 0 6 0
SITEA 1 GRPAPP 11 simpserv TOUPPER 1454599748 1454599748 0 0 0 0 0 5 0
SITEA 1 GRPAPP 10 simpserv LTOUPPER 1454599748 1454599753 60 27 33 0 0 6 0
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |