IBM Support

JR53940: ILLEGAL BUSINESS OBJECT REFERENCE OCCURS WHEN AN OLDER SNAPSHOT RUNS IN PROCESS CENTER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running an older snapshot causes the JavaScript activity to fail
    in an IBM Process Center environment that uses nested business
    objects. You see more information in the following exception:
    
    [6/29/15 19:49:25:655 CEST] 0000012c JavaScriptRun E
    CWLLG2015E:  An unexpected runtime exception occurred. See
    exception for more details.
     Error: com.lombardisoftware.core.TeamWorksException: Property
    <property300> in class <BO200> is not declared. It must be
    declared to be used..
        com.lombardisoftware.core.TeamWorksRuntimeException:
    com.lombardisoftware.core.TeamWorksException: Property
    <property300> in class <BO200> is not declared. It must be
    declared to be used.
    at
    com.lombardisoftware.core.TeamWorksRuntimeException.
    asTeamWorksR
    untimeException(TeamWorksRuntimeException.java:69)
     at com.lombardisoftware.core.TWObject.setPropertyValue
      (TWObject.java:691)
     at com.lombardisoftware.core.script.js.TWObjectScriptable.
      put(TWObjectScriptable.java:505)
     at org.mozilla.javascript.ScriptableObject.
      putProperty(ScriptableObject.java:1729)
     at org.mozilla.javascript.ScriptRuntime.
      setObjectProp(ScriptRuntime.java:1557)
     at org.mozilla.javascript.ScriptRuntime.
      setObjectProp(ScriptRuntime.java:1547)
     at org.mozilla.javascript.Interpreter.interpret
      (Interpreter.java:2487)
     at org.mozilla.javascript.InterpretedFunction.call
      (InterpretedFunction.java:164)
     at org.mozilla.javascript.ContextFactory.doTopCall
      (ContextFactory.java:398)
     at com.lombardisoftware.core.script.JavaScriptContextFactory.
      doTopCall(JavaScriptContextFactory.java:192)
     at org.mozilla.javascript.ScriptRuntime.doTopCall
      (ScriptRuntime.java:3070)
     at org.mozilla.javascript.InterpretedFunction.exec
      (InterpretedFunction.java:175)
     at com.lombardisoftware.core.script.js.JSScript.exec
      (JSScript.java:78)
     at com.lombardisoftware.core.script.js.JavaScriptRunner$2.
      execute(JavaScriptRunner.java:287)
     at com.lombardisoftware.core.script.js.PreparedScope.
      executeWithScope(PreparedScope.java:224)
     at com.lombardisoftware.core.script.js.JavaScriptRunner.
      execute(JavaScriptRunner.java:285)
     at com.lombardisoftware.core.script.js.JavaScriptRunner.
      evalScript(JavaScriptRunner.java:392)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext$1.call(ExecutionContext.java:605)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext$1.call(ExecutionContext.java:603)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext.doWithParams(ExecutionContext.java:739)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext.evalScript(ExecutionContext.java:603)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext.evalScript(ExecutionContext.java:597)
     at com.lombardisoftware.component.twscript.worker.
      ScriptWorker.doJob(ScriptWorker.java:73)
     at com.lombardisoftware.component.common.workflow.
      ExecutionJob.doJob(ExecutionJob.java:461)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.doResumeWorkflowEngine
      (EJBWorkflowManagerBean.java:1431)
    

Local fix

Problem summary

  • In a Process Center environment, you have more than one snapshot
    of a process application and use a nested business object. If
    the newer snapshot removes properties in the nested business
    object (the parent business object is unchanged) and you attempt
    to run the older snapshot, business objects from the newer
    snapshot might be used.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.6.0 that ensures that the
    selected snapshot is used for all nested business objects.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53940:
    
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    
    2. Select APAR or SPR, enter JR53940, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR53940

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-27

  • Closed date

    2015-09-21

  • Last modified date

    2015-09-21

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R856 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 September 2015