Why does the SSM remain at a critical memory level when there is enough available memory and not much unfinished workload?

The SSM may not be able to detect correct memory usage on Linux® under some conditions, and it causes the boundary event not to be triggered properly. In this case, try to set the following environment variables for the SSM in your application profile:

<env name="MMAP_THRESHOLD">131072</env>
<env name="MMAP_MAX">65536</env>