If your users are calling and telling you that App engine processes are remaining in initiated status for longer time ( > 5 minute) and you observe the following message. (Assuming PSAESRV is configured)
in the $PS_CFG_HOME/appserv/prcs/<domain>/LOGS folder for SCHDLR_MMYY.LOG you will see the message
(NET.334): Tuxedo cannot find the service RunAeAsync2. Make sure the application server advertising this service is booted.
To see all files that has this message
grep NET.334 SCHDLR*.LOG | cut -d : -f 1 | sort -u
Please note the number at the end of RunAeAsync. It could be 1 thru n depending on number of PSAESRV configured. What this message means that the PSAESRV and number at the RunAeSync is not running for e.g. in this case PSAESRV that provides service RunAeSync2 is not running.
You will also see in the same folder for TUXLOG.MMDDYY the following message
010135.abc.com!restartsrv.16887.414156544.-2: server AESRV/2: CMDTUX_CAT:1684: ERROR: Application initialization failure
010135.abc.com!restartsrv.16887.414156544.-2: server AESRV/2: CMDTUX_CAT:587: INFO: Cannot restart server, scheduling for cleanup
grep CMDTUX_CAT:1684 TUXLOG.*
What this means is that for some reason PSAESRV has crashed and Tuxedo restart process is not able to restart PSAESRV process.
You have 2 option 2 fix the issue.
Option 1 : Shutdown and Restart the server
Option 2: Manually start the PSAERV process using command line without shutting down and restarting the server.
Option 2 is preferred, if you have other PSAESRV processes running in process monitor that will be killed if you try to stop the process scheduler.
Start PSADMIN (cd $PS_HOME/appserv; ./psadmin)
Select 2 for process Scheduler
Select 1 for Administer a domain
Select 1for appropriate Process Scheduler Domain
Select 5 for TUXEDO command line (tmadmin)
boot -g AESRV -i 1
(Change -I 1 to appropriate number for PSAESRV process that crashed Determined from the number at the end of RunAeSync).
Observed this issue in PeopleTools : 8.53.12 and Linux : Red Hat 6.3 64 bit.