Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
Hi Experts,
I am getting the below error while running XML conc Reports.
+------------- 1) PUBLISH -------------+ Beginning post-processing of request 5940730 on node INDUAPP at 22-NOV-2012 11:22:46. Post-processing of request 5940730 failed at 22-NOV-2012 12:22:45 with the error message: The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
I changed Concurrent: OPP Response Timeout from 360 to 3600 and bounced conc managers.
Still i am getting the same issue.
I am getting the below error while running XML conc Reports.
+------------- 1) PUBLISH -------------+ Beginning post-processing of request 5940730 on node INDUAPP at 22-NOV-2012 11:22:46. Post-processing of request 5940730 failed at 22-NOV-2012 12:22:45 with the error message: The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
I changed Concurrent: OPP Response Timeout from 360 to 3600 and bounced conc managers.
Still i am getting the same issue.
0