Similar to how timeouts can be configured for Oracle Forms, similar timeout features may be implemented for Oracle Reports. Configuring timeouts in Oracle Reports is done in rwserver.conf which is the main configuration file for the reports server. The following configurations may be done in rwserver.conf for configuring timeout:

 

  • Engine Response Timeout
    • Default: null (no timeout)
    • The Engine Response Timeout is how long (in minutes) a report job can run before the reports server engine cancels the job.
    • This is good if a query or report engine is hanging and holding up the queue for other report jobs.
    • Example (15 minutes):
      • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ engineResponseTimeOut=”15”>
  • callbackTimeout
    • Default: 90000
    • The callbackTimeOut is the amount of time (in milliseconds) which the reports server will wait from when the reports server engine is started to when it is called back.
    • Example (100000 ms)
      • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ callbackTimeout=”100000”>
  • maxIdle
    • Default: 30
    • The maxIdle parameter is how long a reports server engine can remain idle before it is terminated. However, this will only work if the value of minEngine is set to 0. If minEngine is set to a value greater than 0, the engine will remain up because the server will be configured to always have an engine running.
    • Example ( 60 min):
      • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ maxIdle=”60”>
Get Our Newsletter