IBM Support

PI66150: LIBERTY SERVER PROCESSES THE START OF WOLA WORKLOAD TOO SLOWLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When workload starts, and the server doesn't process WOLA
    requests until several seconds or minutes have passed.
    

Local fix

  • Set coreThreads in the server.xml
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: WOLA workloads run erratically when the *
    *                      thread pool size is not manually        *
    *                      tuned.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The thread pool for a Liberty server is self-tuning.  When
    running a WOLA workload, a situation can arise when the thread
    pool does not scale up fast enough relative to the number of
    requests that are received.  This can cause requests to time
    out, and in severe situations can cause the Liberty server to
    stop processing all WOLA requests until the thread pool has
    grown to a sufficient size.
    

Problem conclusion

  • Code was added to handle a sudden surge of WOLA requests until
    the thread pool has time to grow to a sufficient size.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 16.0.0.3.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • The executor configuration can be used to manually tune the
    thread pool in server.xml.  The coreThreads setting can be used
    to force the thread pool to start with a minimum number of
    threads, which should roughly correspond to the number of
    concurrent requests you expect to process plus a few extra to
    handle other work.
    

Comments

APAR Information

  • APAR number

    PI66150

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-19

  • Closed date

    2016-08-04

  • Last modified date

    2016-08-04

  • 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

    LIBERTY PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"850","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2020