IBM Support

PH69763: DUPLICATE TASK ID IN SCHEDULER SERVICE

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 multiple JVMs reference the same scheduler database, each
    JVM is expected to receive a unique task ID range to maintain
    task ID uniqueness. However, due to a race condition, the same
    ID range may be assigned to multiple JVMs, resulting in
    duplicate task IDs.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When multiple JVMs are configured to    *
    *                      use the same scheduler database,        *
    *                      duplicate task IDs may be generated.    *
    *                      This can occur intermittently due to    *
    *                      concurrent access, where more than      *
    *                      one JVM receives the same task ID       *
    *                      range. As a result, users may observe   *
    *                      task scheduling conflicts, unexpected   *
    *                      task execution behavior, or errors      *
    *                      related to duplicate task identifiers   *
    *                      in the scheduler database.              *
    ****************************************************************
    During analysis, it was observed that when multiple JVMs connect
    to and use the same scheduler database, a race condition can
    occur while allocating task ID ranges. Due to the lack of proper
    synchronization during this allocation process, the same task ID
    range may be assigned to more than one JVM instance. This leads
    to duplicate task IDs being generated and stored in the
    scheduler database.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH69763

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-01-21

  • Closed date

    2026-03-09

  • Last modified date

    2026-03-10

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
10 March 2026