Direct links to fixes
APAR status
Closed as program error.
Error description
When you use an exposed process variable (EPV) in the default value assignment for a variable in a business process definition (BPD), the process does not start and you see a NullPointerException in the log files that is similar to the following NullPointerException: java.lang.NullPointerException at java.util.Date.getMillisOf(Date.java:950) at java.util.Date.before(Date.java:909) at com.lombardisoftware.client.persistence. EpvVarValueFactory.getCurrentValue (EpvVarValueFactory.java:134) at com.lombardisoftware.core.script.js. AbstractTWEpvVariableScriptable.getDefaultValue (AbstractTWEpvVariableScriptable.java:89) at org.mozilla.javascript.ScriptRuntime.add (ScriptRuntime.java:2561) at org.mozilla.javascript.Interpreter.do_add (Interpreter.java:4669) at org.mozilla.javascript.Interpreter.interpretLoop (Interpreter.java:2958) 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:156) 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:60) at com.lombardisoftware.core.script.js.JavaScriptRunner$2. execute(JavaScriptRunner.java:286) at com.lombardisoftware.core.script.js.PreparedScope. executeWithScope(PreparedScope.java:204) at com.lombardisoftware.core.script.js.JavaScriptRunner. execute(JavaScriptRunner.java:284) at com.lombardisoftware.core.script.js.JavaScriptRunner. evalExpression(JavaScriptRunner.java:401) at com.lombardisoftware.core.script.js.JavaScriptRunner. evalExpression(JavaScriptRunner.java:389) at com.lombardisoftware.bpd.runtime.engine. BPDExecutionTreeNode.evaluateExpression (BPDExecutionTreeNode.java:689) at com.lombardisoftware.bpd.runtime.engine. BPDExecutionTreeNode.evaluateExpression (BPDExecutionTreeNode.java:655) at com.lombardisoftware.bpd.runtime.engine.st. LocalBPDSymbolTable.doInitVariablesDefaultValues (LocalBPDSymbolTable.java:79) at com.lombardisoftware.bpd.runtime.engine.st. LocalBPDSymbolTable.initDefaultValues(LocalBPDSymbolTable. java:51) at com.lombardisoftware.bpd.runtime.engine. BPDExecutionTreeNode.createLocalSymbolTable (BPDExecutionTreeNode.java:934) at com.lombardisoftware.bpd.runtime.engine. RootBPDExecutionTreeNode.<init> (RootBPDExeutionTreeNode.java:42) at com.lombardisoftware.bpd.runtime.engine. BPDExecutionContext.<init>(BPDExecutionContext.java:207) at com.lombardisoftware.bpd.runtime.engine. BPDEngine.<init>(BPDEngine.java:95) at com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore. doStartBPD(BPDEngineServiesCore.java:346) at com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore. doStartBPD(BPDEngineServicesCore.java:267) at com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore. startBPD(BPDEngineServicesCore.java:186) at com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore. startBPD(BPDEngineServicesCore.java:170)
Local fix
You can prevent this issue from recurring by selecting the "In-Progress Tasks Use New Values" check box of the EPV definition.
Problem summary
This issue occurs because the EPV assign date is not set in the process execution context at this early process creation stage. This date is used to determine the currently valid exposed variable value, especially when the "In-Progress Tasks Use New Values" check box on the EPV definition is not selected.
Problem conclusion
A fix is/will be available for IBM BPM that initializes the EPV assign date in the context early enough to be available when the initial values of a variable are calculated. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR51418: 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 JR51418, 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
JR51418
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-10-03
Closed date
2014-11-28
Last modified date
2014-11-28
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
R801 PSY
UP
R855 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021