PQ71449: WebSphere reports an error when OUT params of a CallableStatement are not set.

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
When execute is called for a CallableStatement,
enforceStatementProperties also gets called.  This ensures that
all fields have had set<type> methods called for them.  But with
a CallableStatement, this should not occur.  The customer has a
SQL statement that has several OUT params that are not set prior
to execution, and enforceStatementProperties causes the execute
to fail.
Local fix
If statement caching for the resource is disabled, this problem
does not occur.  This is due to the fact that
enforceStatementProperties does not get called when statement
caching is disabled.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Applications using Callable Statements.      *
*                 The problem only occurs if there are         *
*                 multiple parameters in the callable          *
*                 statement, and some are marked as output     *
*                 parameters.                                  *
****************************************************************
* PROBLEM DESCRIPTION: The number of parameters in a           *
*                      callable statement was being checked,   *
*                      irregardless of whether the parms       *
*                      were marked as input or output.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Parameter count checking was occurring irregardless of whether
the parameter is marked output or input (output parameters do
not have to be specified when a statement is executed).
For example, if a statement had 5 parameters, 1 and 2 are input
(required), 3 and 4 are output, and 5 was another input
parameter, the RelationalResourceAdapter would throw an error.
The error that was thrown indicated that the wrong number of
parameters were specified (in this case it would reach the
third parm, and realize it was not set and throw an exception).
Problem conclusion
The tracking for CallableStatement parameters has been
improved and now includes an indicator for parameter type
(input / output).
Temporary fix Comments
APAR information
APAR number PQ71449
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-02-26
Closed date 2003-03-25
Last modified date 2003-03-25

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
RRA          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ71449
IBM Group: Software Group
Modified date: Mar 25, 2003