IBM Support

JR53785: AFTER APPLYING 8.5.6.0, JSGET_CURRENTTASK THE TASK IS NULL OCCURS EVEN WHEN JR51599 IS IMPLEMENTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Logs are flooded with the following error:
    TWSystemNames E
    com.lombardisoftware.core.script.js.TWSystemNamespaceScriptable
    jsGet_currentTask The task is null; An exception has been caught
     in jsGet_currentTask
    
    JR51599 was introduced to restrict the logging of this benign
    error. The error will only be logged when the tracing is enabled
    at the finest level with the proper trace string.
    However, 8.5.6.0 is still encountering the issue.
    

Local fix

  • N/A
    

Problem summary

  • ABSTRACT ? AFTER APPLYING 8.5.6.0, JSGET_CURRENTTASK THE TASK IS
     NULL OCCURS EVEN WHEN JR51599 IS IMPLEMENTED
    
    ERROR DESCRIPTION -
    When a task is null, logs may be flooded with messages stating a
    null task has been caught. The messages should have been
    optimized in V8.5.6.0 since JR51599 is integrated into the
    refresh pack.
    
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    
    LOCAL FIX -
    None
    
    
    PROBLEM SUMMARY
    During runtime there may be instances where the task execution
    context is null.  For example, the task may be completed already
    and the database has been cleaned up.
    The following log message may be seen the logs repeatedly:
    ?com.lombardisoftware.core.script.js.TWSystemNamespaceScriptable
    jsGet_currentTask The task is null; An exception has been caught
    in jsGet_currentTask
    
    The error does not cause any interruptions during runtime and
    the workflow continues. However, this may cause system logs to
    be overwritten.
    

Problem conclusion

  • The fix is available for IBM BPM v8.5.6.0.  The trace
    specification has been changed to a finer level to prevent this
    message from being logged at higher level trace specifications.
    It should not be logged all the time as the error is benign.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53785:
    
    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 JR53785, and click Continue.
    3.
    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

Comments

APAR Information

  • APAR number

    JR53785

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-09

  • Closed date

    2015-08-09

  • Last modified date

    2015-08-09

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R856 PSY

       UP

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

Document Information

Modified date:
09 August 2015