Fixes are available
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
Customer production system behaving differently in version 8.5.5.11. The connections are not freed and end up getting connectiontimeout exception very few minutes after starting the server. The maxconnection set to 1000 and the numberOfSharedPoolPartitions is set to 200. The 200 is way too low to handle the maxconnection of 1000. Prior to 8.5.5.10 we ignored SharedPoolPartitions value in the advancedconnection pool setting and calculated the value based on Maxconnection. For example, in this case it will be calculated as 2000(1000 max * 2) oppose to 200.
Local fix
The workaround is set to the following values to zero inorder for connection pooling to calculate the value. numberOfSharedPoolPartitions="0" numberOfUnsharedPoolPartitions="0" numberOfFreePoolPartitions="0" freePoolDistributionTableSize="0"
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using advanced connection pool * * properties. * **************************************************************** * PROBLEM DESCRIPTION: Free pool distribution size and * * free pool partions were not being set * * to the correct values resulting in * * performance issues * **************************************************************** * RECOMMENDATION: * **************************************************************** The free pool distribution size and free pool partions are normally set by the connection pool using default values which are the best performance setting. In some cases, the properties do need to be set and the setting were not being used.
Problem conclusion
Setting the free pool distribution size and free pool partions now will set the user values. In general the values should not be used to allow the connection pool to default the values. If a resource adapter supports reauthetication, then the free pool distribution size can be set to 1 which may help to keep the connection pool reduced in size, but this only applies to an idle connection pool or test system. In most production systems, connection are being used at a steady state meaning there may be no difference in performance if the free pool distribution size is to 1 or the connection pool is allow to set it using its defaults. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.43, 8.0.0.14, 8.5.5.12 and 9.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
PI77612
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-06
Closed date
2017-05-10
Last modified date
2017-05-11
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
03 May 2022