Started Purging session. Current Map count 0"2025-11-26 08:20:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 41612025-11-26 08:25:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 25542025-11-26 08:30:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 8912025-11-26 08:35:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 02025-11-26 08:40:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 02025-11-26 08:45:07.327 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 02025-11-26 08:50:07.326 UTC [Timer-0, , , TxId: ] INFO c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 0
VMware HCX 4.11.0 or lower
This is due to web-engine service getting hung due to a known issue, which is caused by an entry in the vCenter, that has a vm-id but no associated entity-name for the same.
This issue is fixed in VMware HCX 4.11.1 and above.
Reference: HCX 4.11.1 Release notes
As a temporary workaround, users can restart web-engine service on hcx. However the threads will start piling up again depending on the usage.