Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
APAR status
Closed as program error.
Error description
The setClientInfo() method unexpectedly resets the value which was previously set on same connection by an application. Here is sample ------------------------- String CLIENT_USER = "ClientUser"; String APPLICATION_NAME = "ApplicationName"; con.setClientInfo(CLIENT_USER, "1234567"); con.setClientInfo(APPLICATION_NAME, (new Date()).toString()); ------------------------- When this application code is run, CLIENT_USER and APPLICATION_NAME were set on the connection object. When closing this connection, the connection would be returned back to the pool,but these values set by the application are reset to NULL and this is unexpected for the application.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: DB2 client properties were reset to * * empty values during connection cleanup * **************************************************************** * RECOMMENDATION: * **************************************************************** Applications use the setClientInfo() API to set the DB2 Client Info properties namely 1)ApplicationName 2)ClientUser 3)ClientHostname 4)ClientAccountingInformation on the connection. In addition, these properties can be set on the datasource as custom properties. Say an application requests a connection (first request). When the connection is created the client info properties from the datasource custom properties are applied on to the connection by application server's adapter. After obtaining the connection, applications can set these properties on the connection object using the setClientInfo() API. Later when the connection is closed, during cleanup, if the application had earlier set the client info properties using setClientInfo() API() then all the client info properties were cleared to empty values before the connection was sent to the free pool. Now when the application requests another connection (second request), the previous connection from the free pool may get picked up and given. In this case the client info properties will have empty values as they were cleared during the cleanup of the previous request. So we end up missing the values set in the datasource custom properties and each getConnection() results in connection objects with different client info property values. To avoid this problem, when the connection is created we hold the initial client info properties before the application attempts to set any properties. Now when the connection is closed, during cleanup before putting back the connection into the freepool we revert back to the initial client info properties.
Problem conclusion
The Relational Resource Adapter (RRA) code has been updated to retain the initial client info property values to be used during reset when the connection is closed. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19 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
PM31082
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-25
Closed date
2011-02-24
Last modified date
2011-02-24
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
Document Information
Modified date:
27 October 2021