PQ68507: UNABLE TO START WEBSPHERE ADMIN SERVER ON HP USING SYBASE 12 AS THE REPOSITORY

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
Can not start the WAS admin server on HP-UX 11i when using
SYBASE 12 as the repository.  Tried running with Sybase on
both the local machine where WAS is installed and running with
the repository on a remote SUN machine, received same errors
when trying to start the WAS admin server.
202d69 ExceptionUtil X CNTR0019E: Non-application
exception occurred while processing method findByPrimaryKey:
java.rmi.RemoteException: ; nested exception is:
not be used in a SELECT which is not part of the declaration
of a cursor or which is  not inside a stored procedure.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Sybase 12 as the repository.                 *
****************************************************************
* PROBLEM DESCRIPTION: Unable to start WebSphere Application   *
*                      Server when using Sybase 12 as the      *
*                      repository, due to connection           *
*                      properties not being set correctly.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem isn't a matter of the JDBC driver overwriting one
set of connectionProperties with another, the problem here is
that if a user sets connectionProperties, the default values
from the portability layer get ignored.
.
In the getDataSource method of PortabilityLayerImpl, there are
two properties object, one passed in based on the configuration
parameters set on the datasource or in the admin.config, and a
set of default properties passed from the specific portability
layer.  If an entry resides in both property objects, as
connectionProperties does in this case, the value passed in is
used and the value from the portability layer is ignored.
.
In cases where the value to the property is a single value,
such as an integer or a boolean, this is the correct behavior.
However, in cases where the property is a String value
containing a list of properties, such as connectionProperties
is, the two Strings need to be combined.  However, they cannot
just be appended together, as it is possible that a user might
override the specific value that the portability layer is
setting.
Problem conclusion
The property objects will be parsed and in the case of duplicate
property specification, the code will use the one passed
in from the configuration.  This problem has been corrected
via internal defect 119886 .
Temporary fix Comments
APAR information
APAR number PQ68507
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-11-22
Closed date 2002-12-26
Last modified date 2002-12-26

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 AI
Fixed component ID 5630A2200

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 #: PQ68507
IBM Group: Software Group
Modified date: Dec 26, 2002