Fixes are available
DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
Setting the QueryTimeout to a non-zero value for a Statement or PreparedStatement object causes the associated resources to be freed only after the timer elapses. If the statement completes prior to the timer elapsing, resources are still held in memory until the timer elapses. If the timer is set to a large value, and the system creates a lot of statements, then an OutOfMemory exception can occur.
Local fix
Local Fix: None Work Around: Set QueryTimeout to 0, or a very low value
Problem summary
Users Affected: JDBC Applications using the Universal JDBC driver only Problem Description: Setting the QueryTimeout to a non-zero value for a Statement or PreparedStatement object causes the associated resources to be freed only after the timer elapses. If the statement completes prior to the timer elapsing, resources are still held in memory until the timer elapses. If the timer is set to a large value, and the system creates a lot of statements, then an OutOfMemory exception can occur. Problem Summary: Setting non-zero QueryTimeout in the Universal JDBC Driver may result in high memory usage in high throughput environments
Problem conclusion
jcc defect 110244 Fixed in: 2.11.82 for v8 stream 3.8.15 for v9.1 (FP7) => http://www-01.ibm.com/support/docview .wss?rs=71&uid=swg21255607 3.52.60 for v9.5 (FP2) => http://www-01.ibm.com/support/docview .wss?rs=71&uid=swg21293566
Temporary fix
Comments
APAR Information
APAR number
LI73362
Reported component name
DB2 UDE ESE LIN
Reported component ID
5765F4104
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-22
Closed date
2009-04-24
Last modified date
2009-06-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
DB2 UDE ESE LIN
Fixed component ID
5765F4104
Applicable component levels
R820 PSY
UP
Document Information
Modified date:
11 June 2009