Server is getting out of memory issues and the environment is using a shared pool for memory management.
Customers have been setting the JVM min and max server values in order to preallocate memory.
As a bad example:
In this case the settings will force the system to always use 4GB of memory. This is not required.
The max memory should always be set to what is able to be used on the system with the baseline OS needs and some overhead calculated in. But there is no need to preallocate memory on the box in a shared memory configuration.
Generally speaking using shared memory is not recommended since there could resource contention on the baremetal solutions and IO related slowdowns.