[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: The history of VST changes by versions

  • Thread starter George Potemkin
  • Start date
Status
Not open for further replies.
G

George Potemkin

Guest
I did not yet deal with the multi-threaded PASOE clients. I see how the multi-threaded servers are represented in _Connect table: Db log: [2019/12/03@09:37:27.498+0300] P-15608 T-15704 I TSRV 1: (452) Login by George on CON:. [2019/12/03@09:37:28.472+0300] P-15608 T-7008 I TSRV 1: (742) Login usernum 24, userid George client type ABL , on GP using TCP/IP IPV4 address 127.0.0.1. [2019/12/03@09:37:59.734+0300] P-15608 T-16004 I TSRV 1: (742) Login usernum 23, userid George client type ABL , on GP using TCP/IP IPV4 address 127.0.0.1. Program: FOR EACH _Connect WHERE _Connect-Usr GT 0: DISPLAY _Connect-Usr _Connect-PID _Connect-TID _Connect-Type _Connect-Server _Connect-ServerPid _Connect-ServerTid. END. _Connect records: User-Id Pid Tid Type Srv Server Pid Server Tid ------- ----- ----- ---- --- ---------- ---------- 1 15608 15704 TSRV ? 0 0 23 12940 2868 REMC 1 15608 16004 24 12940 2868 REMC 1 15608 7008 Server process consists of 3 threads (at least). One of them owns a slot in Usrctl Table. Two other threads serve the remote users but they share the _Connect record with the first thread. Would be the same for the multi-threaded clients? Will the only one thread be represented by a record in _Connect table? We will not have the duplicated values of the _Connect-Usr field, will we? Will the “waits” be reported per _Connect-Usr or per _Connect-Tid? _Connect-Wait _Connect-Wait1 _Connect-Wait2

Continue reading...
 
Status
Not open for further replies.
Top