MSAS Thread (6) crash in Session AS-4. Potential leak 20MB. about iceberg HOT 2 CLOSED

Forgot this part of the logging:

2022-04-12T10:38:37.993+0200 010664 004528 2 AS-7 CcsLevelServices:w:00001ae4 CONN Disconnecting from database assur, user number 10. (9545)
2022-04-12T10:38:37.993+0200 010664 004528 3 AS-7 CcsLevelServices:w:00001ae4 MSAS Adding 'Decrement database' work to Resource Mgr Queue.
2022-04-12T10:38:37.993+0200 010664 004528 3 AS-7 CcsLevelServices:w:00001ae4 MSAS Closing socket, Type: 'Request', Number: 5
2022-04-12T10:38:37.993+0200 010664 004528 4 AS-Aux-0 mtapsv:-:? MSAS csMtPrestartSessions : numSessionsToStart= 0 : maxPoolSize=200 minAvailableSessions=1 numAvailableSessions=0 currSessions=0 numStarting=1
2022-04-12T10:38:37.993+0200 010664 004528 1 AS-Aux-0 mtapsv:-:? MSAS Worker Thread exiting. Number: 7, Status: 10002
2022-04-12T10:38:37.993+0200 010664 004528 3 AS-Aux-0 mtapsv:-:? MSAS Adding 'Dealloc CStack' work to Queue.

from iceberg.

Hi Peter, I'm sorry but you have already opened a support case for the issue you have described, and is the correct path for any further escalations. I would encourage you to continue work with our TS team with regards to use of the metrics and its unexpected impact on an MSAS agent which seems specific to your application. If your question/issue were in regards to the collection of the generated data, use of the tooling provided for reporting, or any action leading up to the activation of the metrics that would be considered an issue against the resources in this repository. Unfortunately I cannot take up this request given the still-open TS case, nor would I suggest that this particular issue be handled in this forum.

from iceberg.