The benefits of PSAESRV versus PSAE are a popular topic of discussion. Our studies have shown that PSAE is as good as
PSAESRV for most practical purposes.
If you have an application engine job that runs longer than 10 seconds, PSAE is equivalent to PSAESRV. PSAE has the added
advantage of being recycled at the end of each application engine job, cleaning up any outstanding SQL cursors to the database
that may have been left behind. Because PSAE recycles after each use, PSAE does not have any possible memory leakage
problem that may occupy the precious system memory. In short, PSAE is a cleaner workhorse.
To shutdown PSAESRV, when you configure the Process Scheduler, you can change the default of the PSAESRV instance to 0.
Values for config section - PSAESRV
Max Instances =0
Recycle Count=1000
Allowed Consec Service Failures=2



  1. Nachu said,

    Ganesh/Sandeep: This is a good post, but setting the value of 'Max Instances=0' under PSAESRV config section in process scheduler configuration won't shutdown or stop the PSAESRV process from booting up. I dont know if you had tried this and it did really work for you.

    But for achieving this, you need to manually configure the process scheduler using 3rd option in psadmin-process scheduler menu, and in that down under there's a option which asks for

    Do you want the Application Engines configured (y/n)? : n

    for which you need to specify [n]. This will suppress the PSAESRV process from booting up. Hope this helps.

    Just FYI: This link gives the reason why one should disable PSAESRV process

    Nachu (the same old Nachu).... lol

    on October 6, 2010 at 6:06 AM