RS01700: SLOW RULESET GENERATION WITHOUT AUTOMATIC BUILD ON DECISION CENTER

Operational Decision Manager V8.5.1.2 Fix Pack
Operational Decision Manager V8.6.0.2 Fix Pack
Operational Decision Manager z/OS 8.7.1.2 Fix Pack
Operational Decision Manager V8.5.1.1: Interim Fix 36

APAR status

• Closed as program error.

Error description

• When many rules are added, then deleted and added again, over
  several such cycles the ruleset generation may start taking a
  long time and possibly result in timeout/rollback exception.
  
  The step that seems to be taking most of the time in ruleset
  generation correspond to the typical stack trace excerpt :
  ...
                  at
  ilog/rules/teamserver/model/impl/IlrAbstractCachingSession.findE
  lements(IlrAbstractCachingSession.java:254(Compiled Code))
                  at
  ilog/rules/teamserver/ejb/ruleset/IlrRulesetArchiveGenerator.fin
  dElementsAndRemoveDuplicates(IlrRulesetArchiveGenerator.java:754
  )
                  at
  ilog/rules/teamserver/ejb/ruleset/IlrRulesetArchiveGenerator.add
  RuleArtifactsToArchiveBuilder(IlrRulesetArchiveGenerator.java:67
  5)
                  at
  ilog/rules/teamserver/ejb/ruleset/IlrRulesetArchiveGenerator.gen
  erateRulesetArchive(IlrRulesetArchiveGenerator.java:246)
                  at
  ilog/rules/teamserver/ejb/service/IlrSessionFacadeImpl.generateR
  CEArchive(IlrSessionFacadeImpl.java:4025)
                  at
  ilog/rules/teamserver/ejb/service/IlrSessionFacadeImpl.generateR
  ulesetArchive(IlrSessionFacadeImpl.java:3979)
  
  
  This also affects the time taken to display a large number of
  artifacts in a Smart View.
  

Local fix

• Configure projects to be "Build automatically" or through the
  Settings wizard set the configuration parameter
  "teamserver.build.elementOnCommit" to true
  

Problem summary

• The queries used to select the rules use outer join and views
  with Derby that are too slow for this process
  

Problem conclusion

• The code is fixed
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• None
  999
  

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R851 PSY

     UP