Hanged reports server engine queues any subsequent requests and freezes the whole Oracle Application Server (OAS).
All the users will see the frozen session.
This is a bug on the Oracle application Server Reports. We cannot manually kill the hung report server engine.
The solution is to set the parameter "engineResponseTimeout" to the engine in the reports server configuration file.
Specify a maximum amount of time in minutes. If the engine takes longer time to update the job status then the report server terminates the job.
To edit the configuration file go to the OAS home and click the report server. "Edit configuration file" link is in the Administration section.
Example is below
Change the values accordingly for your setup.
No comments:
Post a Comment