IBM Support

PK95600: EXPECTEDDURATION PARAMETER IS IGNORE WHEN A TASK IS RUN FROM THE SCHEDULER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ExpectedDuration parameter is ignored when a task is run from
    the Scheduler. WebSphere Application Server always uses the
    transaction timeout as the limit.
    
    A task is started through wsadmin.sh script, with the following
    parameters:
    
    - QOS=2 (QOS_ATLEASTONCE)
    - ExpectedDuration=18000 seconds (5 hours)
    - Total transaction lifetime timeout set to 100 seconds
    - Maximum transaction timeout set to 0 (no limit)
    
    Transaction is canceled 100 seconds later; SystemOut shows:
    
    [8/27/09 11:04:51:271 CEST] 0000001d TimeoutManage I
    WTRN0006W:
    Transaction
    000001235B1821A600000001000002DCDB27BA5A858D1837F3735DA15E040A29
    0688014B
    000001235B1821A600000001000002DCDB27BA5A858D1837F3735DA15E040A29
    0688014B
    00000001
    has timed out after 100 seconds.
    

Local fix

  • none known
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.0.2                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: A transaction started through a         *
    *                      scheduler was incorrectly timed out.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A transaction that is invoked through a scheduler is timing
    out based on the server transaction timeout value rather than
    the expected duration time as specified by the scheduler.
    

Problem conclusion

  • Changed code to ensure that the transaction is started with the
    appropriate timeout value.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.39.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    This is v6.0 equivalent of PK84816.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK95600

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-08

  • Closed date

    2009-09-30

  • Last modified date

    2009-09-30

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022