Allocation Failure in std_server0.out log

[#1]

I am running EP Sp 14 and when I look ing the std_server0.out log under the /usr/sap/SID..../work...I noticed the following:

AF Allocation Failure cannot allocate 4300 bytes etc

EP stays up but when clicking thourhg an error will appear the dispatcher is up ut server is down....5 minutes later server is back up.

I have adjusted the server max param to 1500 M which reduces the error occruence....running on Solaris 64 bit oracle...

Any seen Allocation failure in std_server0.out u

[Former Member]

Allocation failures are a normal part of operation. The reason that it appears that the engine is not running is that the JVM has gone into a stop the world garbage collection. This means that the only thing the VM will do is perform a garbage collection, so your portal requests won't get served. Tuning of the engine is still a bit of an art with SAP as you have seen. The downside to increasing the heap size, which means fewer allocation failures, is that the full garbage collection takes longer. You may want to set your garbage collection to do a paralell sweep phase (I think this is possible with Sun). Check the Sun documentation on how to do this. Garbage collection is divided into three phases. Sweep, Mark, and Compaction. If you set the vm for a parallel sweep phase the engine will keep running while the vm trys to do the sweep phase of the gc. Provided it doesn't have another AF during that time then you won't have an issue where the engine becomes unresponsive.