PQ63670: SETMAXROWS(0) NOT WORKING CORRECTLY WHEN STATEMENT CACHE IS USED | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Customer is using the setMaxRows(0) function to get data. This function is not working correctly when the Prepared statement caching is used. The setMaxRows when set to zero will return the value from the previous setMaxRows request. If the preparedstatement cache is turned off the command runs correctlyLocal fix turn off the preparedstatement cache with datasources.xml or use a high value in the setmaxrowsProblem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users of * * preparedStatement. * **************************************************************** * PROBLEM DESCRIPTION: When using setMaxRows() on * * preparedStatements, once set to a * * finite number, then if the user * * resets it to (0), the Max Rows * * stays at the former number. * **************************************************************** * RECOMMENDATION: * **************************************************************** When caching preparedStatements, the code needed to reset MaxRows to the default (0), which means returning the maximum rows, before returning the statement to the cache.Problem conclusion The Max Rows and two other settings are now set back to the defaults before returning the preparedStatement to the cache.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ60149 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ63670
IBM Group: Software Group
Modified date: Jul 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.