progress / iceberg Goto Github PK
View Code? Open in Web Editor NEWA collection of code, utilities, and guides from real-world customer engagements.
License: Other
iceberg's People
Contributors
Stargazers
Watchers
iceberg's Issues
Ability to trim specific session/agent?
These are very useful tools to monitor PAS, fills the gap since we can no longer use asbman to pull status, stacks and kill procs.
It would be useful (as a feature enhancement) to add the ability to terminate specific sessions/agents instead of all and/or idle, that way we can use this tool to terminate stuck sessions/threads.
What does Utilized Agent-Sessions represent?
Hi,
Using iceberg to monitor PAS instance, the Utilized Agent-Sessions reports a non-zero value when there is nothing running, and I am trying to understand what to make of this.
Is this the same as SessionManager's maxConcurrentClients metric? I noticed in the bracket it says (>3,414 KB).
What does this mean?
[echo] Code Release: 2023-04-23T17:24:41.290 [echo] [echo] NOTICE: Utilities are being executed outside of a PAS instance! [echo] DLC Home: /usr3/dlc [echo] OpenEdge Version: 12.2.11 [PCTRun] Starting output to file: status_training_2023-05-17T07_57_42.763-07_00.txt ... [PCTRun] [PCTRun] Utility Runtime: 12.2.11.0.1427 [PCTRun] Report Executed: 2023-05-17T07:57:42.763-07:00 [PCTRun] PASOE Instance: http://localhost:17128 [PCTRun] [PCTRun] ABL Application Information [training - v12.2.11 ( 2022-11-04 )] [PCTRun] WebApp: ROOT [PCTRun] APSV: ENABLED [PCTRun] SOAP: DISABLED [PCTRun] REST: DISABLED [PCTRun] WEB: DISABLED [PCTRun] [PCTRun] Manager Properties [PCTRun] Maximum Agents: 1 [PCTRun] Minimum Agents: 1 [PCTRun] Initial Agents: 1 [PCTRun] Max. Connections/Agent: 300 [PCTRun] Max. ABLSessions/Agent: 300 [PCTRun] Idle Conn. Timeout: 300,000 ms (00:05:00.000) [PCTRun] Idle Session Timeout: 1,800,000 ms (00:30:00.000) [PCTRun] Idle Agent Timeout: 1,800,000 ms (00:30:00.000) [PCTRun] Idle Resource Timeout: 300,000 ms (00:05:00.000) [PCTRun] Conn. Wait Timeout: 3,000 ms (00:00:03.000) [PCTRun] Request Wait Timeout: 15,000 ms (00:00:15.000) [PCTRun] Initial Sessions/Agent: 60 [PCTRun] Min. Avail. Sess/Agent: 1 [PCTRun] [PCTRun] > Agent PID 12845746: AVAILABLE [PCTRun] Est. Agent Lifetime: 22:39:12.937 [PCTRun] DynMax ABL Sessions: 300 [PCTRun] Total ABL Sessions: 60 [PCTRun] Avail ABL Sessions: 60 [PCTRun] Open Connections: 0 [PCTRun] Overhead Memory: 171,222 KB [PCTRun] [PCTRun] SESSION ID STATE STARTED LIFETIME SESS. MEMORY BOUND/ACTIVE CLIENT SESSION [PCTRun] 4 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 12,616 KB - [PCTRun] 7 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 8 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 9 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 10 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 11 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 12 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 7,163 KB - [PCTRun] 13 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 14 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 15 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 16 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 13,034 KB - [PCTRun] 17 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 18 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 19 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 20 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 21 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 22 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 23 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 24 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 25 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 26 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 27 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 28 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 29 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 30 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 31 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 32 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 33 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 34 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 35 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 36 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 37 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 38 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 39 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 40 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 41 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 42 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 43 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 44 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 45 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 46 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 47 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 48 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 49 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 50 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 51 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 52 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 53 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 54 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 55 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 56 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 57 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 58 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 59 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 60 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 61 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 62 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 63 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 64 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] 65 IDLE 05/16/2023 09:18:29.937+07:00 22:39:12.937 3,413 KB - [PCTRun] Active Agent-Sessions: 0 of 60 (0% Busy) [PCTRun] Utilized Agent-Sessions: 3 of 60 (>3,414 KB) [PCTRun] Approx. Agent Memory: 398,605 KB [PCTRun] [PCTRun] Session Manager Metrics (Count-Based) [PCTRun] [PCTRun] Client HTTP Sessions: 0 [PCTRun]
"status" task when using w/11.7.15 causes ABL error 3135
OE 11.7.15. Instance stafrted and running under that version. The instance is newly-created with almost no modifications ( a couple of webhandlers added).
Iceberg running from source; or at least as-is from a git clone on the repo.
The proant status command is run from an 11.7 proenv shell.
In addition to the error 3135 in the output, none of the ABL sessions are shown in the output.
c:\Work\git\iceberg\PAS\Management\OEManager\ABL>proant status
Buildfile: c:\Work\git\iceberg\PAS\Management\OEManager\ABL\build.xml
status:
[echo] Code Release: 2022-11-08T14:50:26.421
[echo] DLC Home: C:\Progress\OPENED~4
[echo] OpenEdge Version: 11.7.15
[PCTRun] Starting output to file: status_dvfs2_2022-12-11T20_16_14.112-05_00.txt ...
[PCTRun]
[PCTRun] Utility Runtime: 11.7.15.0.2183
[PCTRun] Report Executed: 2022-12-11T20:16:14.113-05:00
[PCTRun] PASOE Instance: http://localhost:8810/
[PCTRun]
[PCTRun] ABL Application Information [dvfs2 - v11.7.15 ( 2022-05-31 )]
[PCTRun] WebApp: ROOT
[PCTRun] APSV: ENABLED
[PCTRun] SOAP: ENABLED
[PCTRun] REST: ENABLED
[PCTRun] WEB: ENABLED
[PCTRun]
[PCTRun] Manager Properties
[PCTRun] Maximum Agents: 10
[PCTRun] Minimum Agents: 0
[PCTRun] Initial Agents: 1
[PCTRun] Max. Connections/Agent: 16
[PCTRun] Max. ABLSessions/Agent: 200
[PCTRun] Idle Conn. Timeout: 300,000 ms (00:05:00.000)
[PCTRun] Idle Session Timeout: 300,000 ms (00:05:00.000)
[PCTRun] Idle Agent Timeout: 300,000 ms (00:05:00.000)
[PCTRun] Idle Resource Timeout: 0 ms (00:00:00.000)
[PCTRun] Conn. Wait Timeout: 3,000 ms (00:00:03.000)
[PCTRun] Request Wait Timeout: 15,000 ms (00:00:15.000)
[PCTRun] Initial Sessions/Agent: 2
[PCTRun] Invalid handle. Not initialized or points to a deleted object. (3135)
[PCTRun]
[PCTRun] > Agent PID 70128: AVAILABLE
[PCTRun] Est. Agent Lifetime: 00:12:08.576
[PCTRun]
[PCTRun] SESSION ID STATE STARTED LIFETIME SESS. MEMORY BOUND/ACTIVE CLIENT session
[PCTRun] active Agent-Sessions: 0 of 0 (0% Busy)
[PCTRun] Utilized Agent-Sessions: 0 of 0 (>801 KB)
[PCTRun] Approx. Agent Memory: 0 KB
[PCTRun]
[PCTRun] Session Manager Metrics (Count-Based)
[PCTRun]
[PCTRun] Client HTTP Sessions: 5
[PCTRun] STATE SESS STATE BOUND LAST ACCESS / STARTED ELAPSED time session MODEL ADAPTER session ID REQUEST ID
[PCTRun]
[PCTRun] RUNNING RESERVED NO 2022-12-11T20:12:06.732-0500 00:04:07.490 SESSION_FREE WEB UkA_pelZQS6L61_DxpBbYA ROOT:w:0000001d
[PCTRun] |- ClientConn: [127.0.0.1](http://127.0.0.1/) 2022-12-11T20:12:06.727-0500 00:04:07.495 Proc: Progress.Web.InternalWebHandler:HandleRe
[PCTRun] |-- AgentConn: PID 70128 RESERVED Agent: /0.0.0.0:62002 Local: /192.168.42.123:59475
Agent memory metrics reported by proant status do not match what the OS is reporting for the _mproaps process?
Hello,
I am using iceberg to manage our PAS instance, when using the proant status command, the various memory metrics reported do not match what the OS level process is consuming.
In the example below, I have an OEPAS APSV ABL session running that is consuming large amounts of memory, but none of the metrics inside the tool add up to the total memory being consumed by the process.
Buildfile: /usr/local/iceberg/build.xml
status:
[echo] Code Release: 2022-07-07T11:56:15.191
[echo] DLC Home: /usr3/dlc
[echo] OpenEdge Version: 12.2.10
[PCTRun] Starting output to file: status_training_2022-10-27T09_51_03.891-07_00.txt ...
[PCTRun]
[PCTRun] Utility Runtime: 12.2.10.0.1386
[PCTRun] Report Executed: 2022-10-27T09:51:03.894-07:00
[PCTRun] PASOE Instance: http://localhost:17128
[PCTRun]
[PCTRun] ABL Application Information [training - v12.2.10 ( 2022-06-10 )]
[PCTRun] WebApp: ROOT
[PCTRun] APSV: ENABLED
[PCTRun] SOAP: DISABLED
[PCTRun] REST: DISABLED
[PCTRun] WEB: DISABLED
[PCTRun]
[PCTRun] Manager Properties
[PCTRun] Maximum Agents: 1
[PCTRun] Minimum Agents: 1
[PCTRun] Initial Agents: 1
[PCTRun] Max. Connections/Agent: 300
[PCTRun] Max. ABLSessions/Agent: 300
[PCTRun] Idle Conn. Timeout: 300,000 ms (00:05:00.000)
[PCTRun] Idle Session Timeout: 1,800,000 ms (00:30:00.000)
[PCTRun] Idle Agent Timeout: 1,800,000 ms (00:30:00.000)
[PCTRun] Idle Resource Timeout: 0 ms (00:00:00.000)
[PCTRun] Conn. Wait Timeout: 3,000 ms (00:00:03.000)
[PCTRun] Request Wait Timeout: 15,000 ms (00:00:15.000)
[PCTRun] Initial Sessions/Agent: 60
[PCTRun] Min. Avail. Sess/Agent: 1
[PCTRun]
[PCTRun] > Agent PID 14484034: AVAILABLE
[PCTRun] Est. Agent Lifetime: 01:09:08.549
[PCTRun] DynMax ABL Sessions: 300
[PCTRun] Total ABL Sessions: 33
[PCTRun] Avail ABL Sessions: 32
[PCTRun] Open Connections: 2
[PCTRun] Overhead Memory: 866,162 KB
[PCTRun]
[PCTRun] SESSION ID STATE STARTED LIFETIME SESS. MEMORY BOUND/ACTIVE CLIENT SESSION
[PCTRun] 4 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 7,449 KB -
[PCTRun] 7 ACTIVE 10/27/2022 08:41:55.463+07:00 01:09:08.549 5,434 KB -
[PCTRun] 8 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 9 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 10 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 11 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 12 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 13 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 14 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 15 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 16 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 17 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 18 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 19 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 20 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 22 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 23 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 26 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 29 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 31 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 32 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 34 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 35 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 38 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 42 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 45 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 49 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 50 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 53 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 56 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 62 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 63 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] 65 IDLE 10/27/2022 08:41:55.463+07:00 01:09:08.549 3,521 KB -
[PCTRun] Active Agent-Sessions: 1 of 33 (3% Busy)
[PCTRun] Utilized Agent-Sessions: 2 of 33 (>3,522 KB)
[PCTRun] Approx. Agent Memory: 988,192 KB
[PCTRun]
[PCTRun] Session Manager Metrics (Count-Based)
[PCTRun] # Requests to Session: 201
[PCTRun] # Agent Responses Read: 473 (0 Errors)
[PCTRun] # Agent Requests Written: 404 (0 Errors)
[PCTRun] Concurrent Connected Clients: 1 (Max: 6)
[PCTRun] # Reserve ABLSession Waits: 0
[PCTRun] # Reserve ABLSession Timeout: 0
[PCTRun]
[PCTRun] Client HTTP Sessions: 1
[PCTRun] STATE SESS STATE BOUND LAST ACCESS / STARTED ELAPSED TIME SESSION MODEL ADAPTER SESSION ID REQUEST ID
[PCTRun]
[PCTRun] RUNNING RESERVED NO 2022-10-27T09:50:59.569-0700 00:00:04.498 SESSION_FREE APSV 7F9C029DBBBA14BFD1AC1E82A2B0499FD2753E3EB092.training ROOT:a:0000020e
[PCTRun] |- ClientConn: 172.16.104.254 2022-10-27T09:50:59.569-0700 00:00:04.498 Proc: mytest123.p
[PCTRun] |-- AgentConn: PID 14484034 RESERVED Agent: xxx-xxxxx/172.16.4.16:17129 Local: /172.16.4.16:37852
[PCTRun]
BUILD SUCCESSFUL
Total time: 0 seconds
Looking at the OS level topas utility, it reports 26GB for the _mproapsv process.
Name PID CPU% PgSp Owner
_mproaps 14484034 2.0 26.3G prosvr
java 16843502 1.8 39.9M root
java 5505790 0.1 130M prosvr
perl5.28 22086076 0.1 5.43M lpar2rrd
reaffin 459030 0.0 640K root
java 21234068 0.0 124M prosvra
bash 17105498 0.0 1.05M root
topas 15270370 0.0 9.75M mirde
ipsec_lo 22020564 0.0 1020K root
_mproaps 22348164 0.0 23.2M prosvr
_mprosrv 23527926 0.0 2.41M prodb
java 19268342 0.0 148M prosvr
_mprosrv 23462254 0.0 2.39M prodb
vtiol 655644 0.0 6.31M root
java 20251242 0.0 148M prosvra
nvme_kpr 5570882 0.0 1.25M root
swapper 520 0.0 448K root
_mprshut 20840770 0.0 2.07M prodb
Exiting from topas1 0.0 872K root
Is there a way to report on what ABL agent session is using up the memory? In this case, my test case program (mytest123.p) is written to allocate a bunch of memory on purpose for testing, but that is not being reported inside the tool.
Is there a way for the tool to report on what agent session is holding onto this memory? In this case, it should be session id 7.
Activate metrics shutdown available agent
I have implemented the monitor and application on OpenEdge 12.2.3.
When activate the metrics on the application I encountered the following behavior.
The metrics was set on the available agent. The agent shutdown and a new agent was started.
The new agent was not available during the activate procedure. Basically the monitor on this application was only pushing his short live time info to the monitor.
Solution is an upgrade to 12.2.7 or higher.
Invalid handle. Not initialized or points to a deleted object. (3135)
Updating iceberg to latest March release and running oemanager status is not working, it is returning:
Buildfile: /usr3/wrk/traininga/utils/oemanager.xml
status:
[echo] Code Release: 2023-04-23T17:24:41.290
[echo]
[echo] DLC Home: /usr1/dlc
[echo] OpenEdge Version: 12.2.11
[PCTRun] Starting output to file: status_traininga_2023-04-23T17_33_39.797-07_00.txt ...
[PCTRun]
[PCTRun] Utility Runtime: 12.2.11.0.1427
[PCTRun] Report Executed: 2023-04-23T17:33:39.798-07:00
[PCTRun] PASOE Instance: http://localhost:17160
[PCTRun] Invalid handle. Not initialized or points to a deleted object. (3135)
[PCTRun]
[PCTRun] Manager Properties
[PCTRun]
[PCTRun] No MSAgents running
[PCTRun]
[PCTRun] Session Manager Metrics (Not Enabled)
[PCTRun]
[PCTRun] Client HTTP Sessions: 0
[PCTRun]
BUILD SUCCESSFUL
Reverting back to an older build of iceberg (version before utils.zip deployment to PAS instance), I don't run into the same issue.
Not sure why this is happening, appreciate any help. would like to keep my local iceberg instance in sync with latest from this repo.
MSAS Thread (6) crash in Session AS-4. Potential leak 20MB.
We run progression test on our PAS. This generates over a thousand Web Service Requests. Takes several hours to finalize.
All requests are getting through with a few exceptions. So now we would like to trace on memory leaks using the iceberg tool.
When I activate the metrics on the PAS each request on the Web Service Requests is crashing on a potential leak.
2022-04-12T10:38:34.509+0200 010664 004528 1 AS-7 CcsLevelServices:w:00001ae4 DEBUG WebservicesHandler - ctor
2022-04-12T10:38:34.512+0200 010664 004528 1 AS-7 CcsLevelServices:w:00001ae4 DEBUG WebservicesHandler.HandleRequest - start
2022-04-12T10:38:37.881+0200 010664 004528 1 AS-7 CcsLevelServices:w:00001ae4 MSAS Thread (7) crash in Session AS-7. Potential leak 19MB.
2022-04-12T10:38:37.881+0200 010664 004528 4 AS-7 CcsLevelServices:w:00001ae4 MSAS sending session info to broker : num_user_sessions= 0
2022-04-12T10:38:37.881+0200 010664 004528 4 AS-7 CcsLevelServices:w:00001ae4 MSAS sending session info to broker : sock= 1132
2022-04-12T10:38:37.881+0200 010664 004528 4 AS-7 CcsLevelServices:w:00001ae4 MSAS sending session info to broker : disown sock= 1132
2022-04-12T10:38:37.881+0200 010664 004528 4 AS-7 CcsLevelServices:w:00001ae4 MSAS sending session info to broker : own sock= 1132
2022-04-12T10:38:37.881+0200 010664 004528 4 AS-7 CcsLevelServices:w:00001ae4 MSAS session info message sent ... status= 0
2022-04-12T10:38:37.881+0200 010664 004528 3 AS-7 CcsLevelServices:w:00001ae4 MSAS csMtSendABLSessionInfo : session info message sent to broker: num_sessions= 0
2022-04-12T10:38:37.881+0200 010664 004528 3 AS-7 CcsLevelServices:w:00001ae4 MSAS Adding 'Close all procedure libraries' work to Resource Mgr Queue.
2022-04-12T10:38:37.882+0200 010664 004528 2 AS-7 CcsLevelServices:w:00001ae4 CONN Disconnecting from database dwh, user number 5. (9545)
Big question here is, Why does it crash on a potential memory leak?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.