In EBS context file there are below 3 AF variables,
AF_JRE_TOP
AF_CLASSPATH
AFJVAPRG.
If these variables are not set correctly then resolve it by following below steps that is referenced in note ,
1. Check how the Concurrent Manager sees your environment variables while running a concurrent program
- Log into Applications as the System Administrator - Navigate: Request -> Run - Choose Single Request - Choose "Prints Environments Variables" concurrent request - Enter AF_CLASSPATH, AF_JRE_TOP, AFJVAPRG - Submit program
2. Make the following change on your TEST system - Backup your adovars.env file - Update AF_CLASSPATH, AF_JRE_TOP, AFJVAPRG in your adovars.env using the full paths - Bounce the Concurrent Managers - Run the "Prints Environment Variables" Concurrent request to check the values - Test a Java Concurrent Program.
AF variables are set for letting programs know the location of java (AFJVAPRG), JRE (AF_JRE_TOP) and the classpath (AF_CLASSPATH) on the concurrent node. Also, note that these variables are also set on the web node.
==>Query to get the workflow notification mailer logfile to troubleshoot issues.
select fl.meaning,fcp.process_status_code, decode(fcq.concurrent_queue_name,'WFMLRSVC','mailer container','WFALSNRSVC','listener container',fcq.concurrent_queue_name) "CONTAINER", fcp.concurrent_process_id,os_process_id, fcp.logfile_name from fnd_concurrent_queues fcq, fnd_concurrent_processes fcp , fnd_lookups fl where fcq.concurrent_queue_id=fcp.concurrent_queue_id and fcp.process_status_code='A' and fl.lookup_type='CP_PROCESS_STATUS_CODE' and fl.lookup_code=fcp.process_status_code and concurrent_queue_name in('WFMLRSVC','WFALSNRSVC') order by fcp.logfile_name;
