PQ58535: USER NAME PROPERTY MISSING IN DRIVERMANAGER.GETCONNECTION

 A fix is available

4.0.2-4.0.7: Component cumulative Connection Manager fix



APAR status
Closed as program error.

Error description
Customer would like to maintain configuration similar to 3.5 and
NOT enter any passwords into WebSphere configuration as they
belong to the application owners and not to the infrastructure
owners. Even though the default userid/password are set to "",
customer cannot get rid of the user/pass pari in the properties.
Setting them to "" receives jz004 : user name property missing
in DriverManager.getConnection(..., Properties). Setting them to
" " yields java.sql.SQLException JZ00L login failure.
Customer is specifying:
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource as the
implementation class but it seems WebSphere is making incorrect
use of it. If they do not want to specify the defaults and
require the userid/password be specified when acquiring the
connection.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of    *
*                 Sybase or Informix as the database.          *
****************************************************************
* PROBLEM DESCRIPTION: In WebSphere 4.0, a userid and password *
*                      is required to be entered into the WAS  *
*                      configuration.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In 3.5, WebSphere didn't require the entering of a userid or
password into the WAS configuration.  This information belongs
to the application owners and not to the infrastructure
owners.  When the default userid and password are set to
"", the user is not able to get rid of the uid/pw parameter
in the properties.  Setting them to "" receives jz004:user name
property missing in DriverManager.getConnection().
Setting them to " " yields java.sql.SQLException JZ00L login
failure.
.
This problem occurs with both Sybase and Informix.  The issue
is that in order to determine which portability layer to use
(Sybase or Sybase11, Informix or Informix7) a connection
must be obtained to check the meta data.  To get this
connection, a user id and password must be passed from the
getConnection call in DataSourceImpl to the getPortabilityLayer
call on SybasePortabilityLayer or PortabilityLayerImpl
(Informix).
Problem conclusion
Added two fields, tmpUser and tmpPassword to the
datasource properties object, which is available in all of
the necessary classes.
Temporary fix Comments
APAR information
APAR number PQ58535
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-02-28
Closed date 2002-03-27
Last modified date 2002-03-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDBC          

SRLS

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58535
IBM Group: Software Group
Modified date: Mar 27, 2002