IBM Support

JR56844: YOU SEE "THE 'DECORATEDMESSAGE' ARGUMENT CANNOT BE 'NULL'" ERRORWHEN RUNNING THE BPMSNAPSHOTCLEANUP COMMAND

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you try to run the BPMSnapshotCleanup command on an IBM
    Process Center environment, the command fails and you see the
    following error in the SystemOut.log file:
    
    [10/14/16 19:15:56:451 EDT] 0000014e wle           E
    CWLLG2229E: An exception occurred in an EJB call.  Error: The
    'decoratedMessage' argument cannot be 'null'.
    
    com.lombardisoftware.client.delegate.BusinessDelegateException:
    The 'decoratedMessage' argument cannot be 'null'.
     at
    com.lombardisoftware.client.delegate.BusinessDelegateException.a
    sBusinessDelegateException(BusinessDelegateException.java:46)
     at
    com.lombardisoftware.client.delegate.BPDEngineServicesDelegateDe
    fault.findBPDInstances(BPDEngineServicesDelegateDefault.java:418
    )
     at
    com.lombardisoftware.server.ejb.repositoryservices.SnapshotDelet
    eSupport.queryBPDInstNum(SnapshotDeleteSupport.java:180)
     at
    com.lombardisoftware.server.ejb.repositoryservices.SnapshotDelet
    eSupport.deleteSnapshotBulkWithBPDInstDel(SnapshotDeleteSupport.
    java:324)
     at
    com.lombardisoftware.server.ejb.repositoryservices.RepositorySer
    vicesCore.snapshotCleanupWithinTX(RepositoryServicesCore.java:52
    0)
    ...
     at
    com.ibm.bpm.pal.commands.impl.internal.BPMSnapshotCleanup.execut
    e(BPMSnapshotCleanup.java:97)
    Caused by: com.lombardisoftware.core.TeamWorksException: The
    'decoratedMessage' argument cannot be 'null'.
     at
    com.lombardisoftware.core.TeamWorksException.asTeamWorksExceptio
    n(TeamWorksException.java:136)
     at
    com.lombardisoftware.bpd.runtime.monitor.BPDMonitorDAO.findBPDIn
    stances(BPDMonitorDAO.java:113)
     at
    com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore.findBP
    DInstances(BPDEngineServicesCore.java:1303)
    ...
     ... 92 more
    Caused by: java.lang.IllegalArgumentException: The
    'decoratedMessage' argument cannot be 'null'.
     at
    com.lombardisoftware.core.TeamWorksDecoratingException$MessageDe
    coder.<init>(TeamWorksDecoratingException.java:501)
     at
    com.lombardisoftware.core.TeamWorksDecoratingException.newDecode
    r(TeamWorksDecoratingException.java:277)
     at
    com.lombardisoftware.bpd.runtime.monitor.BPDInstanceSearchResult
    .<init>(BPDInstanceSearchResult.java:74)
     at
    com.lombardisoftware.bpd.runtime.monitor.BPDMonitorDAO.findBPDIn
    stances(BPDMonitorDAO.java:96)
     ... 111 more
    
    You can observe the same error also when doing one of the
    following:
    
    - Running the BPMDeleteSnapshot command on a Process Server
    environment
    
    - Using the inspector of the desktop or web Process Designer
    

Local fix

  • You can delete, retry or terminate the process instances that
    cause the query result parser to fail. Perform the following
    database query to identify those instances:
    
    SELECT * FROM LSW_BPD_INSTANCE WHERE EXECUTION_STATUS=3 AND
    ERROR IS NULL
    
    Then use one of the available options to delete these instances,
    for example
    
    - run the BPMProcessInstancesPurge command using the
      -instanceStatus FAILED and -instanceID {piid} parameters
    
    - run the REST API: DELETE
      /rest/bpm/wle/v1/process/{piid}?action=delete&parts=none
    
    Or to retry the process instance:
    
    - run the REST API: PUT
      /rest/bpm/wle/v1/process/{piid}?action=retry&parts=none
    
    Or to terminate the process instance:
    
    - run the REST API: POST
      /rest/bpm/wle/v1/process/{piid}?action=terminate&parts=none
    

Problem summary

  • When cleaning up snapshots, the system checks if there are still
    instances for this snapshot. The result parser for the
    corresponding database query fails if the query returns process
    instances in the Failed state, but there re no error details.
    

Problem conclusion

  • A fix will be included in IBM BPM V8.5.7 cumulative fix (CF)
    2016.12. The fix ensures the result parser correctly handles
    query response items that include a process instance in the
    Failed state, even when there are no error details.
    
    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.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR56844

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-19

  • Closed date

    2016-11-23

  • Last modified date

    2016-11-23

  • 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

  • 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":"855","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 November 2016