IBM Support

PI15809: eXtreme Scale creates two ORB thread pools during initialization.

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

  • eXtreme Scale proceses can get OutOfMemoryError errors related
    to too many threads when eXtreme Scale initializes the ORB
    used. This problem does not exist when running in a WebSphere
    Application Server process since the WebSphere Application
    Server runtime initializes the ORB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere eXtreme Scale who are    *
    *                  using                                       *
    *                  the                                         *
    *                  ORB transport outside of a WebSphere        *
    *                  Application Server process.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: An influx of threads is created when    *
    *                      starting an eXtreme Scale process       *
    *                      like a catalog, container, client, or   *
    *                      xscmd.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    eXtreme Scale initialized the ORB in such a way that the ORB
    created
    its
    default thread pool and
    then waited for eXtreme Scale to replace that thread pool with
    the
    one that it created. The initialization logic was updated to
    correctly cause the ORB to only use the eXtreme Scale thread
    pool.
    

Problem conclusion

  • An interim fix is available for this APAR.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI15809

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-11

  • Closed date

    2014-05-21

  • Last modified date

    2014-05-21

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R711 PSY

       UP

  • R850 PSY

       UP

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 May 2014