IBM Support

PM58584: WORKMANAGER THREADPOOL VALUES INCORRECT WHEN VIEWING FROM ADMINISTRATIVE CONSOLE AND ITCAM

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The max threadpool value for the DefaultWorkmanager is not
    correct.
    
    The WorkManager makes a request for a threadpool and is given
    a value of 1 for the lowerBound and 5 for the upperBound.
    Performance Monitoring Infrastructure (PMI) counters for the
    WorkManager ThreadPool gets initialized with these values.
    
    Later when the WorkManager updates the values for upperBound and
    lowerBound the PMI component is not notified so the values
    remain the same at 1 and 5.
    
    These wrong values are then reflected on the administrative
    console and in ITCAM instead of the correct values that the
    WorkManager was changed to.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Upper bound and Lower bound values      *
    *                      for PMI counter poolSize shows          *
    *                      incorrect values for Default Work       *
    *                      manager.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The max threadpool value for the DefaultWorkmanager is not
    correct.
    The WorkManager makes a request for a threadpool and this given
    a value of 1 for the lowerBound and 5 for the upperBound. PMI
    counters for the WorkManager ThreadPool gets initialized with
    these values.
    Later when the WorkManager updates the values for upperBound
    and
    lowerBound the PMI component is not notified so the values
    remain the same at 1 and 5.
    These wrong values are then reflected on the administrative
    console and in ITCAM instead of the correct values that the
    WorkManager was changed to.
    

Problem conclusion

  • This happens mainly because Default Work Manager when it
    requests creation of a threadPool does not pass the Maximum and
    Minum Size of the pool(Which is not mandatory). When the
    threadPool  is created PMI counters are initialized, at which
    point the default values for Max and Min are taken which are 5
    and 1. After PMI counter initialization ,WorkManager code
    updates the Maximum and Minimum values for the threadPool,
    which are not notified to the PMI counter.
    
    Code has been modified from Runtime and PMI perspectives to
    handle this situation and update the upper and lower bounds of
    the Default Work Manager threadPool correctly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.45, 7.0.0.25, and 8.0.0.5.  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

    PM58584

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-20

  • Closed date

    2012-05-15

  • Last modified date

    2012-07-17

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM58584

Modified date: 17 July 2012