PQ73701: ClassNotFound Exception while creating sybase datasource on WAS 4.0.4 and WAS 4.0.5

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
In WAS 4.0.4 or WAS 4.0.5, after creating the Sybase JDBC
provider through the console and wscp but when try to create a
sybase datasource
 ClassNotFound exception is thrown on
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource.
Local fix
Fall back to WAS 4.0.3.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users who   *
*                 use multiple vendor's databases.             *
****************************************************************
* PROBLEM DESCRIPTION: This problem arose when a script was    *
*                      used to create multiple datasources. A  *
*                      ClassNotFoundException could be thrown. *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem was that when using multiple vendor's databases,
the user could get the exception two ways, one was using the
testConnection button on subsequent datasources where both were
not the repository.  Another way to reproduce the problem was
to define two or more datasources in a script where neither
were the repository.
Problem conclusion
In the past, we created one classLoader and tried to use it
for all of the datasources.  In a one or two DB environment,
which is the vast majority of our customers, this would work.
But when another database vendor's driver was added, the same
ClassLoader was used, resulting in the  ClassNotFoundException.
The way we created classLoaders for the JDBC drivers was
redesigned.  We now allow as many as need be, creating a new
classLoader for each.
Temporary fix Comments
APAR information
APAR number PQ73701
Reported component name WEBSPHERE AE SO
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-04-30
Closed date 2003-04-30
Last modified date 2003-04-30

APAR is sysrouted FROM one or more of the following:
PQ73231

APAR is sysrouted TO one or more of the following:

Modules/Macros
NONE JDBC        

Publications Referenced

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

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: 00A
Software edition:
Reference #: PQ73701
IBM Group: Software Group
Modified date: Apr 30, 2003