IBM Support

PI52309: WebSphere Liberty default executor auto-tuning is disabled when an embedder overrides the default ThreadFactory.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere Liberty default executor allows embedders to
    override the default ThreadFactory implementation by
    registering a new ThreadFactory with the OSGi service
    registry.  When this new ThreadFactory is injected into the
    default executor, a new thread pool is created that uses the
    new ThreadFactory, however the default executor auto-tuning
    code is not informed of the change which means that it fails
    to start monitoring the new thread pool for throughput and
    tuning it accordingly.  The new thread pool will remain at
    the default values for coreThreads and maxThreads.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Liberty default executor auto-*
    *                      tuning is disabled when an embedder     *
    *                      overrides the default ThreadFactory.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Liberty default executor allows embedders to
    override the default ThreadFactory implementation by registering
    a new ThreadFactory with the OSGi service registry.  When this
    new ThreadFactory is injected into the default executor, a new
    thread pool is created that uses the new ThreadFactory, however
    the default executor auto-tuning code is not informed of the
    change which means that it fails to start monitoring the new
    thread pool for throughput and tuning it accordingly.  The new
    thread pool will remain at the default values for coreThreads
    and maxThreads.
    

Problem conclusion

  • Code was added so that when a custom ThreadFactory is injected
    into the default executor, the auto-tuning code is informed of
    the resulting new thread pool.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.9.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI52309

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-11

  • Closed date

    2016-02-23

  • Last modified date

    2016-02-23

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021