Issue:
Concurrent Program failed:Output post processor is running has not picked up this request
Concurrent request marked as warning.
User not able to make payment.
Cause:
When this error occurs in one report, subsequent reports will likely not have any output and will end up with errors also.
To obtain the Output Post Processor log file, follow the navigation below:
1. Select the System Administrator responsibility.
2. Select the menu Concurrent – Manager – Administer.
3. Select the Output Post Processor Service.
4. Select the Processes button.
5. Select Manager Log.
6. The log will contain a java stack error similar to the following:
[8/26/20 6:00:40 AM] [103250:RT93139933] Completed post-processing actions for request 93139933.
java.lang.OutOfMemoryError: GC overhead limit exceeded”
Solution:
To resolve the issue we need to increase the heap size that requires concurrent bonce but in my environment we don’t have downtime. So we implemented the following workaround to fix the issue.
1) Bounce the oacore services in the rolling fasion.
Stop oacore using “admanagedsrvctl.sh stop oacore_server1”
Start oacore using “admanagedsrvctl.sh start oacore_server1”
Stop oacore using “admanagedsrvctl.sh stop oacore_server2”
Start oacore using “admanagedsrvctl.sh start oacore_server2”
Stop oacore using “admanagedsrvctl.sh stop oacore_server3”
Start oacore using “admanagedsrvctl.sh start oacore_server3”
Note: bouncing the oacore service which we are sure will resolve the issue (temporarily) and it did as expected. Basically when you bounce the services all the existing connections and processess will be released which results in more available memory when you re-start the services.
After we retest the issue user able to make payment.
