IBM Support

PI76916: RTC WORK ITEMS PLUGIN: CONCURRENT ADD WORK ITEM COMMENT STEPS INCONSISTENTLY FAIL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Running multiple Add Work Item Comment steps in parallel aimed
    at the same
    work item may fail with a olsc status code of 409. This is
    caused by multiple requests hitting the same work item property
    and RTC not being able to manage the simultaneous requests.
    

Local fix

  • Add a retry if a status code of 409 is found.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * RTC Work Items plugin v8 or lower for UrbanCode Deploy.      *
    * Customers running Add Work Item Comments steps               *
    * simultaneously against the same work item.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The user will receive random crashing due to these requests  *
    * colliding with one another on RTC. This will show itself as  *
    * a 409 error, which means the work item is not ready to       *
    * accept changes.                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to version 9+ of the RTC Work Items plugin.          *
    ****************************************************************
    This error will occur randomly because it depends on the timing
    of when the request are hitting the RTC server.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI76916

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    611

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-20

  • Closed date

    2017-05-01

  • Last modified date

    2017-05-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

  • R620 PSN

       UP

  • R620 PSY

       UP

  • R621 PSN

       UP

  • R621 PSY

       UP

  • R622 PSN

       UP

  • R622 PSY

       UP

  • R623 PSN

       UP

  • R623 PSY

       UP

  • R624 PSN

       UP

  • R624 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 May 2017