Concurrent-->Manager-->Administer ->query for the Output Post Processor where you can see restart option
I have done that, but it just hang and can not fixed itself. There maybe hardcore issues that is happening internally.
Is there some scripts to cleanup the error? stop cm , clean up, and start again? without bouncing the entire apps?
Please follow the below steps.
1,System Administator > Concurrent > Manager > Administer
2,Query "Output Post Processor" -> Processes button
Get the sytem id of "Output Post Processor"
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query "Output Post Processor" -> Restart button
1. Shutdown the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there is no FNDLIBR processe running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/apps
What is Output Post Processor?
Concurrent Processing now uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.Post-processing actions are actions taken on concurrent request output. An example of a post-processing action is that used in Concurrent Processing support of XML Publisher.
If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.
Can I run cmclean.sql even if the apps is running?
I was told that apps should be down when you run it.
No need to bring down the all application services. You can bring down the ICM using adcmctl.sh and run cmclean.sql.