Announcement

Collapse
No announcement yet.

[SOLVED] Automatically Killing Long-Running Reports

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [SOLVED] Automatically Killing Long-Running Reports

    Hello,

    Had a problem with long-running reports (over 16 hours) for one of our clients. This was causing the Oracle Reports server to slow down incredibly and was putting a considerable strain on the OTM DB server.

    In order to resolve this, we found a parameter for Oracle reports 10.1.2.0.2 that allows the reports engine to automatically kill threads that have run too long: engineResponseTimeOut

    Change:
    Code:
    <engine id="rwEng" class="oracle.reports.engine.EngineImpl" initEngine="10" maxEngine="20" minEngine="10" engLife="50" maxIdle="30" callbackTimeOut="90000" jvmOptions="-Xms128m -Xmx1024m -Xss512k">
    To:
    Code:
    <engine id="rwEng" class="oracle.reports.engine.EngineImpl" initEngine="10" maxEngine="20" minEngine="10" engLife="50" maxIdle="30" callbackTimeOut="90000" engineResponseTimeOut="30" jvmOptions="-Xms128m -Xmx1024m -Xss512k">
    Where the value (in this case 30) is the number of minutes to let a report run before automatically killing it.

    Hope this helps!

    Thanks,
    Chris
    Last edited by chrisplough; October 5, 2007, 22:41.
    Chris Plough
    twitter.com/chrisplough
    MavenWire
Working...
X