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

Fixes are available

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

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

Document Information

Modified date:
28 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?