Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
showPoolContents should not return the value of other datasource mbeans when the mapped datasouce mbean returns null. wsadmin showPoolContents returns value of other datasource when it returns null value. For example : DataSource1 : "O1Delay1" Connection created. Datasource2 : "DefaultD" No connection created get the datasource1 object. _mbean=AdminControl.queryNames('name=OlDelay1,type=DataSource,no de=Node02,process=server1,*') Print showPoolContents print AdminControl.invoke(_mbean, 'showPoolContents') Everything looks good up to this point. It shows only the information about DataSource1. Now , get the datasource2 object _mbean=AdminControl.queryNames('name=DefaultD,type=DataSource,no de=Node02,process=server1,*') Print showPoolContents print AdminControl.invoke(_mbean, 'showPoolContents') It first shows Null and then dumps any other available pool information. The ConnectionPool for DefaultDatasource was null. The ConnectionPool will be created when the first connection request is processed if connections have been created in the pool, an internal error has occurred. Followed by all other datasource information.
Local fix
Ignore other datasource values
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application server * * who use wsadmin to invoke showPoolContents * **************************************************************** * PROBLEM DESCRIPTION: showPoolContents when invoked from * * wsadmin returns the pool contents of * * all datasources even though the pool * * contents were requested for one * * datasource which has a pool value of * * null. * * For instance, * * DataSource1 : "O1Delay1" Connection * * created. * * Datasource2 : "DefaultD" No connection * * created * * _mbean=AdminControl.queryNames('name=O1 * * Delay1,type=DataSource,node=Node02,proc * * ess=server1,*') * * print AdminControl.invoke(_mbean, * * 'showPoolContents') * * The above command shows only the pool * * contents of O1Delay1. * * _mbean=AdminControl.queryNames('name=De * * faultD,type=DataSource,node=Node02,proc * * ess=server1,*') * * print AdminControl.invoke(_mbean, * * 'showPoolContents') * * The above command first shows Null * * and then dumps any other available * * pool information.In this instance when * * showPoolContents is invoked for * * DefaultD, the pool contents as null * * is displayed followed by the pool * * contents of O1Delay1. * **************************************************************** * RECOMMENDATION: * **************************************************************** While checking for a null pool manager , the whole hashmap which stores the cfkey to pool contents was being printed hence the first time when showPoolContents was invoked for a null pool manager, only the message gets printed however when invoked the second time or third time after invoked for datasources whose pool contents is not null then this problem would occur.
Problem conclusion
The problem has been fixed. The fix for this APAR is currently targeted for inclusion in fixpack 8.5.5.4,8.0.0.10 and 7.0.0.37 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
PI15051
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-02
Closed date
2014-09-08
Last modified date
2014-09-08
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022