You observe policy server fails to startup following a Linux OS patching activity and a system reboot. The Policy Server logs (smps.log) contain the following error sequence:
[AssertionGenerator.java][ERROR][sm-FedServer-00120] postProcess() throws exception: java.lang.NoClassDefFoundError: Could not initialize class java.lang.ProcessEnvironmentAnd then a lot of:
[AssertionGenerator.java][ERROR][sm-FedServer-00120] postProcess() throws exception: java.lang.NoClassDefFoundError: Could not initialize class com.netegrity.SAML2Security.SAML2EncryptDecrypt
The issue is caused by a "post-reboot storm" where multiple services start simultaneously, leading to a temporary exhaustion of system resources (such as process limits, memory, or file handles). If the Policy Server JVM tries to initialize its environment access at the exact moment resources are unavailable, the java.lang.ProcessEnvironment class fails to load. The class remains in an error state for the life of the process, causing subsequent class (such as SAML2EncryptDecrypt) initialization failure.
You can resolve this by delaying the startup of the Policy Server to allow the operating system to complete other service initializations and stabilize resource availability.
Locate your Policy Server auto-startup script (init script, or a script used by systemd service file).
Modify the script to include a sleep command before the policy server "start-all" script. For example,
sleep 120Consult your Linux administrator to ensure the system limits are sufficient to handle the concurrent startup of all services. Check and increase the following if necessary:
nprocnofile