IBM Support

JR62464: SERVICE-RESULT CACHING MIGHT NOT WORK CORRECTLY FOR LINKED SERVICE FLOWS, NESTED SERVICES WHEN RETRYING FAILED STEPS

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.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • To improve performance, you could enable service-result caching
    by selecting "Enable caching of service flow results" for a
    service flow. Service result caching is supported for top-level
    service flows but not for linked service flows.
    
    A service flow might return a cached result from a service flow
    run earlier even if service result caching is disabled if all
    the following conditions are met:
    
    - The service flow is called from a system task in a process and
    "Delete task on completion" is deselected on the system task.
    - The service flow calls a linked service flow and "Enable
    caching of service flow results" is selected for this service
    flow.
    - There is an activity in the linked service flow that saves the
    execution context, such as a script task where "Save execution
    context" is selected.
    - The service flow fails after the linked service flow was
    called, and the process is put in the "Failed" state.
    - You "Retry failed steps" for your process, such as by using
    Process Inspector.
    
    Service-result caching doesn't work correctly when "Delete task
    on completion is disabled", and the execution context is saved
    in nested service flows.
    
    Note: This interim fix also applies to services in the desktop
    IBM Process Designer.
    
    PRODUCTS AFFECTED
    IBM Business Automation Workflow
    

Local fix

  • Disable service-result caching on the linked service flow.
    

Problem summary

  •   This issue occurs because the service result cache setting is
      incorrectly used from a linked service flow during a retry of
      the failed steps from a process when the execution context of
      the service flow was saved.
    

Problem conclusion

  • A fix is available or will be available that ensures
    service-result caching is performed correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62464

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    J00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-22

  • Closed date

    2020-08-25

  • Last modified date

    2020-08-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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0.1"}]

Document Information

Modified date:
14 December 2020