LO76487: DERBY.INDEX-STAT-THREAD USES EXCESSIVE CPU

APAR status

• Closed as program error.

Error description

• After updating from older releases of Traveler CPU usage may
  have increased due to a bug in the Derby DB component.  A thread
   named "derby.index-stat-thread" will consume excessive CPU and
  degrade DB and system performance.
  

Local fix

• Configure derby setting that will prevent index stats from being
   updated automatically (derby.storage.indexStats.auto=false)
        - Create file <domino data>\traveler\derby.properties
        - Add one line to this file:
           derby.storage.indexStats.auto=false
        - Restart Traveler to pick up this configuration change
  Note: remove this file after APAR has been applied
  

Problem summary

• After multiple upgrades the derby database may use higher than
  normal CPU.  This problem is only seen after upgrade of a stand
  alone Notes Traveler server.
  

Problem conclusion

• The Notes Traveler server was updated to turn off by default the
  auto storage stats which were driving the high CPU.
  

Temporary fix

• This issue is fixed in Notes Traveler 9.0.0.1 IF1 and later
  releases.  See this technote for the latest available
  maintenance information:
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LOTUS NOTES TRA

• Fixed component ID

  5724E6204

Applicable component levels

• R900 PSY

     UP