IBM Support

JR55729: YOU RECEIVE A NULLPOINTEREXCEPTION WHEN RUNNING A HERITAGE HUMAN SERVICE AFTER UPGRADING TO IBM BPM V8.5.6

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When you run a heritage human service after upgrading IBM
    Business Process Manager (BPM) to V8.5.6 or V8.5.7, the service
    fails.
    In the server SystemOut.log file, you see an exception like the
    following exception:
    Ä4/9/16 22:25:13:124 CDTÜ 000001d2 EJBWorkflowMa E   CWLLG0594E:
    An exception occurred while initializing the runnable thread.
    Error: java.lang.NullPointerException
    java.lang.NullPointerException
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.getSymbolTableDifferencesAsJSON
      (EJBWorkflowManagerBean.java:2100)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.generateStayOnUiResult
      (EJBWorkflowManagerBean.java:1998)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.doResumeWorkflowEngine
      (EJBWorkflowManagerBean.java:1462)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.resumeTask
      (EJBWorkflowManagerBean.java:359)
     at com.lombardisoftware.server.ejb.workflow.
      EJSRemoteStatefulEJBWorkflowManager_82478d70.
      resumeTask(Unknown Source)
     at com.lombardisoftware.server.ejb.workflow.
      _EJBWorkflowManagerInterface_Stub.resumeTask
      (_EJBWorkflowManagerInterface_Stub.java:347)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateDefault.resumeTask
      (EJBWorkflowManagerDelegateDefault.java:107)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateWebSphere$2.run
      (EJBWorkflowManagerDelegateWebSphere.java:52)
     at java.security.AccessController.doPrivileged
      (AccessController.java:341)
     at com.lombardisoftware.client.delegate.common.
      WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive
      (WebsphereDelegateHelper.java:204)
     at com.lombardisoftware.client.delegate.common.
      WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive
      (WebsphereDelegateHelper.java:188)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateWebSphere.resumeTask
      (EJBWorkflowManagerDelegateWebSphere.java:50)
     at com.lombardisoftware.component.common.web.
      WebWorkflowManager.callEJBWorkflowManager
      (WebWorkflowManager.java:930)
     at com.lombardisoftware.component.common.web.
      WebWorkflowManager.processScreen(WebWorkflowManager.java:893)
     at com.lombardisoftware.component.common.web.
      WebWorkflowManager.processRequest
      (WebWorkflowManager.java:355)
     at com.lombardisoftware.servlet.AjaxControllerServlet.doPost
      (AjaxControllerServlet.java:154)
    

Local fix

Problem summary

  • IBM BPM V8.5.0 introduced an objectId property in the metadata
    of a business object to identify the business object.
    
    This property is automatically filled when a business object is
    created. When navigation in a heritage human service from a
    coach step returns to the same coach step?either by using wires
    or a Stay On Page event?the coach is not completely refreshed;
    only the changed data applies.
    
    IBM BPM V8.5.6 enhanced the logic to use the objectId property
    to determine which data changed. This enhanced logic is used
    only for process applications that use the system toolkit in
    V8.5.6 or a later releases. However, this logic fails because
    the objectId is not set when you have an IBM BPM deployment
    environment earlier than V8.5.0 with active instances and you
    perform the following steps:
    
    1. Upgrade the IBM BPM deployment environment to V8.5.6 or
      V8.5.7.
    
    2. Install a new snapshot of your process application that uses
      the new system toolkit version.
    
    3. Migrate active instances to that new snapshot.
    
    4. Run a heritage human service.
    

Problem conclusion

  • A fix that automatically initialized the objectId property when
    it is not yet set will be included in an upcoming IBM Business
    Process Manager (BPM) V8.5 cumulative maintenance vehicle.
    
    To determine whether the cumulative fix is available and
    download it if it is, complete the following steps on Fix
    Central:
    
    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 Text, enter ?cumulative fix?, and click Continue.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR55729

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-11

  • Closed date

    2016-05-25

  • Last modified date

    2016-05-25

  • 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

  • R857 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:
25 May 2016