RS01137: NullPointerException when parsing ruleset with sequential ruletask

WebSphere ILOG JRules V7.1.1.5 Fix Pack
WebSphere ILOG Rule Team Server V7.1.1.5 Fix Pack
Operational Decision Manager V8.0.1 Download Document
WebSphere Operational Decision Management V7.5.0.3 Fix Pack

APAR status

• Closed as program error.

Error description

• When parsing a ruleset with a sequential task the following
  exception is thrown. If there is no sequential task there is no
  error generated and the execution succeeds.
  Exception in thread "main" java.lang.NullPointerException
   at ilog.jit.lang.IlxJITIndexExpr.getType(Unknown Source)
   at ilog.rules.engine.sequential.k.a(Unknown Source)
   at ilog.rules.engine.sequential.k.exploreValue(Unknown
  Source)
   at
  ilog.rules.engine.base.IlrMethodValue.exploreValue(Unknown
  Source)
   at ilog.rules.engine.sequential.k.i(Unknown Source)
   at ilog.rules.engine.sequential.k.exploreValue(Unknown
  Source)
   at
  ilog.rules.engine.base.IlrRtUnaryValue.exploreValue(Unknown
  Source)
   at ilog.rules.engine.sequential.k.i(Unknown Source)
   at ilog.rules.engine.sequential.c.exploreTest(Unknown
  Source)
   at ilog.rules.engine.base.IlrTrueTest.exploreTest(Unknown
  Source)
   at ilog.rules.engine.sequential.c.try(Unknown Source)
   at ilog.rules.engine.sequential.h.exploreStatement(Unknown
  Source)
   at ilog.rules.engine.base.IlrRhsIf.exploreStatement(Unknown
  Source)
   at ilog.rules.engine.sequential.h.a(Unknown Source)
   at ilog.rules.engine.sequential.i.a(Unknown Source)
   at ilog.rules.engine.sequential.i.if(Unknown Source)
   at ilog.rules.engine.sequential.i.byte(Unknown Source)
   at ilog.rules.engine.sequential.i.try(Unknown Source)
   at
  ilog.rules.engine.sequential.IlrTupleMatcherRulesetJitter.transl
  ate(Unknown Source)
   at
  ilog.rules.engine.sequential.IlrTupleMatcherRulesetJitter.transl
  ate(Unknown Source)
   at
  ilog.rules.engine.sequential.platform.IlrSEQTaskFactory.a(Unknow
  n Source)
   at
  ilog.rules.engine.sequential.platform.IlrSEQTaskFactory.newTaskI
  mpl(Unknown Source)
   at ilog.rules.engine.IlrRuleset$4.run(Unknown Source)
   at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:202)
   at ilog.rules.engine.IlrRuleset.generateTaskImpl(Unknown
  Source)
   at ilog.rules.engine.IlrRuleset$3.run(Unknown Source)
   at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:202)
   at ilog.rules.engine.IlrRuleset.a(Unknown Source)
   at ilog.rules.engine.IlrPackage.a(Unknown Source)
   at ilog.rules.engine.IlrRuleset.for(Unknown Source)
   at ilog.rules.engine.IlrRuleset.a(Unknown Source)
   at ilog.rules.engine.IlrRulesetArchiveParser.for(Unknown
  Source)
   at
  ilog.rules.engine.IlrRulesetArchiveParser.parseArchiveFactory(Un
  known Source)
   at
  ilog.rules.engine.IlrRulesetArchiveParser.parseArchive(Unknown
  Source)
   at
  ilog.rules.engine.IlrRulesetArchiveParser.parseArchive(Unknown
  Source)
   at
  ilog.rules.engine.IlrRulesetArchiveParser.parseArchive(Unknown
  Source)
  

Local fix

• fi functions are used, ensue that no variables are created
  without initialization
  

Problem summary

• When multiple variables are defined it is possible that because
  they have the same default value they are declared identical.
  This leads to error during execution because the type expected
  does not match the type of the variable used.
  

Problem conclusion

• The code is modified to prevent this side effect
  

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

• R800 PSY

     UP