IBM Support

PJ45314: A NOCLASSDEFFOUNDERROR EXCEPTION OCCURS AND THE ICM_RULESOPERATION CAN'T PROCESS FURTHER RULES

Direct links to fixes

IBM Case Manager V5.3.3 Interim Fix 10 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 10 for Windows
IBM Case Manager V5.3.3 Interim Fix 10 for SUSE Linux
IBM Case Manager V5.3.3 Interim Fix 10 for Linux
IBM Case Manager V5.3.3 Interim Fix 10 for AIX
IBM Case Manager V5.3.3 Interim Fix 10 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 10 for Windows
IBM Case Manager V5.3.3 Interim Fix 10 for SUSE Linux
IBM Case Manager V5.3.3 Interim Fix 10 for Linux
IBM Case Manager V5.3.3 Interim Fix 10 for AIX
IBM Case Manager V5.3.3 Interim Fix 9 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 9 for Windows
IBM Case Manager V5.3.3 Interim Fix 9 for Linux
IBM Case Manager V5.3.3 Interim Fix 9 for AIX
IBM Case Manager V5.3.3 Interim Fix 8 for Windows
IBM Case Manager V5.3.3 Interim Fix 8 for Linux
IBM Case Manager V5.3.3 Interim Fix 8 for AIX
IBM Case Manager V5.3.3 Interim Fix 7 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 7 for Windows
IBM Case Manager V5.3.3 Interim Fix 7 for Linux
IBM Case Manager V5.3.3 Interim Fix 7 for AIX
IBM Case Manager V5.3.3 Interim Fix 6 for Linux
IBM Case Manager V5.3.3 Interim Fix 6 for AIX
IBM Case Manager V5.3.3 Interim Fix 6 for Windows
IBM Case Manager V5.3.3 Interim Fix 6 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 4 for Linux
IBM Case Manager V5.3.3 Interim Fix 4 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 4 for Windows
IBM Case Manager V5.3.3 Interim Fix 4 for AIX
IBM Case Manager V5.3.3 Interim Fix 3 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 3 for Windows
IBM Case Manager V5.3.3 Interim Fix 3 for Linux
IBM Case Manager V5.3.3 Interim Fix 3 for AIX
IBM Case Manager V5.3.3 Interim Fix 5 for Linux for Z
IBM Case Manager V5.3.3 Interim Fix 5 for Windows
IBM Case Manager V5.3.3 Interim Fix 5 for Linux
IBM Case Manager V5.3.3 Interim Fix 5 for AIX
IBM Case Manager V5.3.3 Interim Fix 1 for Linux for System Z
IBM Case Manager V5.3.3 Interim Fix 1 for Windows
IBM Case Manager V5.3.3 Interim Fix 1 for Linux
IBM Case Manager V5.3.3 Interim Fix 1 for AIX
workflow.18001.delta.repository

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When IBM Case Manager is configured with IBM FileNet P8 Content
    Platform Engine V5.2.1.6/7, the ICM_RulesOperation component, in
     the process of executing a rule, results in the following error
     in the pesvr_system.log file after deploy a solution:
    
    2018/03/19 11:14:08.665-0700 RPCHandler PEPrimary8 [Error]
    CMExecute[2].<dbuser>.<datasource>.ICM_RuleOperations.<user>
    [<taskName>:1EDA3318XXXXXX48XXXXEDXXXXXX68B:Workflow:executeRule
    ] FAILED.; Exception: java.lang.NoClassDefFoundError:
    ilog/rules/bres/xu/event/IlrErrorEvent
            at
    com.ibm.rules.res.xu.log.internal.LogHandler.severe(LogHandler.j
    ava:249)
            at
    ilog.rules.res.xu.cci.IlrXUInteraction.execute(IlrXUInteraction.
    java:263)
            at
    com.ibm.rules.res.xu.client.internal.XUSession.executeOperation(
    XUSession.java:156)
            at
    com.ibm.rules.res.xu.client.internal.XURuleEngineSession.execute
    RuleEngineOperation(XURuleEngineSession.java:60)
            at
    com.ibm.rules.res.xu.client.internal.XURuleEngineSession.getRule
    setArchiveProperties(XURuleEngineSession.java:604)
            at
    ilog.rules.res.session.impl.IlrStatefulSessionBase.<init>(IlrSta
    tefulSessionBase.java:112)
            at
    ilog.rules.res.session.impl.IlrStatefulSessionBase.<init>(IlrSta
    tefulSessionBase.java:81)
            at
    ilog.rules.res.session.impl.j2se.IlrStatefulSessionJ2SE.<init>(I
    lrStatefulSessionJ2SE.java:34)
            at
    ilog.rules.res.session.IlrJ2SESessionFactory.createStatefulSessi
    on(IlrJ2SESessionFactory.java:145)
            at
    ilog.rules.res.session.impl.IlrSessionFactoryBase.createStateful
    Session(IlrSessionFactoryBase.java:158)
            at
    com.ibm.acm.rules.shared.runtime.RulesRuntimeUtility.getParamete
    rInfo(RulesRuntimeUtility.java:305)
            at
    com.ibm.acm.rules.shared.runtime.RulesRuntimeUtility.executeRule
    (RulesRuntimeUtility.java:175)
            at
    com.ibm.casemgmt.ruleops.RuleOperations.executeRule(RuleOperatio
    ns.java:253)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
            at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:95)
    ....
            at
    com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:19
    6)
            at
    com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:15
    3)
            at
    sun.reflect.GeneratedMethodAccessor17.invoke(UnknownSource)
            at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:56)
            at java.lang.reflect.Method.invoke(Method.java:620)
            at
    com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:239)
            at
    com.filenet.api.util.UserContext.doAs(UserContext.java:151)
            at
    filenet.jpe.cm.CMExecuteAStepTask$TaskWorker.call(CMExecuteAStep
    Task.java:144)
            at
    filenet.jpe.cm.CMExecuteAStepTask$TaskWorker.run(CMExecuteAStepT
    ask.java:189)
            at
    filenet.jpe.cm.CMExecuteAStepTask.doMyJob(CMExecuteAStepTask.jav
    a:318)
            at
    filenet.jpe.cm.CMDispatcherTask.process(CMDispatcherTask.java:40
    8)
            at
    filenet.jpe.cm.CMDispatcherTask.doMyJob(CMDispatcherTask.java:17
    0)
            at filenet.jpe.cm.CMBaseTask.doJob(CMBaseTask.java:112)
            at
    filenet.jpe.server.common.DelayBackgroundTask.run(DelayBackgroun
    dTask.java:232)
            at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1157)
            at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:627)
            at java.lang.Thread.run(Thread.java:809)
    
    On the application server SystemOut.log, the following is
    logged:
    
    [3/19/18 11:14:08:665 PDT] 00000125 SystemOut     O 3/19/18
    11:14:08 AM [SEVERE]    GBRXU0001E /<Target Object
    Store>_<SolutionPrefix>/10.0/<Solution Rule Name>/1.0 7.6 -
    Theinteraction ruleset.getInformation has failed.
    javax.resource.ResourceException:
    com.ibm.rules.res.xu.internal.XUException: GBRXU0436E: The
    ruleset parsing process failed.
        at
    ilog.rules.res.xu.spi.IlrManagedXUConnection.createResourceExcep
    tion(IlrManagedXUConnection.java:876)
        at
    ilog.rules.res.xu.spi.IlrManagedXUConnection.getXURulesetArchive
    Information(IlrManagedXUConnection.java:1263)
        at
    ilog.rules.res.xu.cci.IlrXUConnection.getXURulesetArchiveInforma
    tion(IlrXUConnection.java:466)
        at
    ilog.rules.res.xu.cci.IlrXUInteraction.getRulesetInformation(Ilr
    XUInteraction.java:561)
        at
    ilog.rules.res.xu.cci.IlrXUInteraction.dispatchExecution(IlrXUIn
    teraction.java:129)
        at
    ilog.rules.res.xu.cci.IlrXUInteraction.execute(IlrXUInteraction.
    java:253)
        at
    com.ibm.rules.res.xu.client.internal.XUSession.executeOperation(
    XUSession.java:156)
        at
    com.ibm.rules.res.xu.client.internal.XURuleEngineSession.execute
    RuleEngineOperation(XURuleEngineSession.java:60)
        at
    com.ibm.rules.res.xu.client.internal.XURuleEngineSession.getRule
    setArchiveProperties(XURuleEngineSession.java:604)
    ....
        at java.lang.reflect.Method.invoke(Method.java:620)
        at
    com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:239)
        at
    com.filenet.api.util.UserContext.doAs(UserContext.java:151)
        at
    filenet.jpe.cm.CMExecuteAStepTask$TaskWorker.call(CMExecuteAStep
    Task.java:144)
        at
    filenet.jpe.cm.CMExecuteAStepTask$TaskWorker.run(CMExecuteAStepT
    ask.java:189)
        at
    filenet.jpe.cm.CMExecuteAStepTask.doMyJob(CMExecuteAStepTask.jav
    a:318)
        at
    filenet.jpe.cm.CMDispatcherTask.process(CMDispatcherTask.java:40
    8)
        at
    filenet.jpe.cm.CMDispatcherTask.doMyJob(CMDispatcherTask.java:17
    0)
        at filenet.jpe.cm.CMBaseTask.doJob(CMBaseTask.java:112)
        at
    filenet.jpe.server.common.DelayBackgroundTask.run(DelayBackgroun
    dTask.java:232)
        at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1157)
        at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:627)
        at java.lang.Thread.run(Thread.java:809)
    Caused by: com.ibm.rules.res.xu.internal.XUException:
    GBRXU0436E: The ruleset parsing process failed.
        at
    com.ibm.rules.res.xu.ruleset.IlrRulesetParsingWork.run(IlrRulese
    tParsingWork.java:97)
        ... 1 more
    Caused by: java.lang.NullPointerException
        at java.io.Reader.<init>(Reader.java:90)
        at
    java.io.InputStreamReader.<init>(InputStreamReader.java:119)
        at
    ilog.rules.factory.IlrReflect.loadPath(IlrReflect.java:292)
        at
    ilog.rules.engine.IlrRulesetArchiveParser.loadBom(IlrRulesetArch
    iveParser.java:1376)
        at
    ilog.rules.engine.IlrRulesetArchiveParser.loadArchive(IlrRuleset
    ArchiveParser.java:746)
        at
    ilog.rules.engine.IlrRulesetArchiveParser.parseArchive(IlrRulese
    tArchiveParser.java:729)
        at
    com.ibm.rules.res.xu.engine.cre.internal.RulesetParser.parseArch
    ive(RulesetParser.java:73)
        at
    ilog.rules.res.xu.ruleset.factory.internal.IlrXURulesetFactory.c
    reateCRERuleset(IlrXURulesetFactory.java:316)
        at
    ilog.rules.res.xu.ruleset.factory.internal.IlrXURulesetFactory.c
    reateRuleset(IlrXURulesetFactory.java:116)
        at
    com.ibm.rules.res.xu.ruleset.IlrRulesetParsingWork.run(IlrRulese
    tParsingWork.java:91)
        ... 1 more
    
    Issue is intermittent but seems to generally happen after a
    solution deployment.
    Once the issue occurs, the errors will continue and no further
    work will process correctly from the ICM_RulesOperation
    component queue.
    

Local fix

  • The following can be done to recover the component queue:
    1) Restart the CPE application server node
    2) disable the ICM_RulesOperations component queue and re-enable
    it.
      a. Go into ACCE, navigate to the ICM_RulesOperations component
    queue.
      b. Uncheck 'enable component processing', save the changes.
      c. Then re-check the box and save, to re-enable the processing
    of rules.
    

Problem summary

  • No additional information is available.
    

Problem conclusion

  • A fix that ensures the ICM_RulesOperation component calls no
    longer result in a NoClassDefFoundError exception after a
    solution deploys will be included in a future release of IBM
    Business Automation Workflow.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ45314

  • Reported component name

    CASE MGR CLIENT

  • Reported component ID

    5725A1501

  • Reported release

    531

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-04

  • Closed date

    2018-06-18

  • Last modified date

    2018-06-18

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

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

    PJ45323

Fix information

  • Fixed component name

    CASE MGR CLIENT

  • Fixed component ID

    5725A1501

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTJ4","label":"Case Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"531","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 September 2022