Persistent Memory Retention in Sakai 20 - Seeking Fixes for High-Concurrency Exam Cycles

[AUMS Team]

Background: We are running Sakai 20 (10GB Heap) at a large university. We frequently host multiple large-scale assessments on the same day.

The Problem: We are observing severe memory retention where objects from one exam session are not released before the next session begins.

The "Restart" Requirement: Currently, we are forced to restart the server after every exam session.

Observation: Memory does not drop even after 24 hours of idle time or after a manual Full GC.

Verification: jmap -histo:live confirms that thousands of instances of org.sakaiproject.site.impl.BaseSite and Samigo PublishedAssessment objects remain strongly referenced in the heap long after student sessions have ended.

Impact: This "staircase" memory growth prevents us from running a standard full-day exam schedule without manual intervention (restarts), which carries significant operational risk.

Is there any settings to configure this behaviour in sakai.properties?

Is this handled in Sakai 25?