Fixes are available
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.45: Java SDK 1.6 SR16 FP60 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 following warning messages are logged repeatedly in the SystemOut.log with a datasource configured with Microsoft JDBC Driver connecting to Microsoft SQL Server. [7/31/13 8:56:06:301 EDT] 0000014e WSRdbManagedC W DSRA1300E: Feature is not implemented: javax.sql.PooledConnection. addStatementEventListener. [7/31/13 8:56:06:301 EDT] 0000014e WSRdbManagedC W DSRA1300E: Feature is not implemented: javax.sql.PooledConnection. removeStatementEventListener.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: DSRA1300E: "Feature is not * * implemented: * * javax.sql.PooledConnection.addStatement * * EventListener" logged repeatedly * **************************************************************** * RECOMMENDATION: * **************************************************************** The warning messages are issued because the JDBC driver claims to be a JDBC 4.0 compliant driver (by returning DatabaseMetaData.getJDBCMajorVersion= 4), but it's implementation of javax.sql.PooledConnection does not implement the addStatementEventListener and removeStatementEventListener interfaces". WebSphere Application Server logs these messages while adding and removing the statement listeners and can fill up the SystemOut.log. Per JDBC 4.0 specifications, --------------------------------------- 11.7 Statement Events If the connection pool manager supports Statement pooling for PreparedStatement objects, it must implement the StatementEventListener interface and then be registered as a listener by that PooledConnection object. --------------------------------------- This warning message was already changed into a debug message from V8.0 and above. We are using this APAR for V7.0 to log this message as a debug instead of warning message. This will avoid the SystemOut.log getting filled up with these warning messages.
Problem conclusion
The WebSphere adapter (RRA) component has been updated to log these messages as part of debug instead of warnings. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.33. 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
PM95559
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
2013-08-21
Closed date
2013-12-05
Last modified date
2013-12-05
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:
01 November 2021