Mark,
Did you ever have any luck looking into this? I have
found that if I explicitly set the "user" and
"password" parameters for each database in WebSphere
(rather than using a container managed JAAS
authentication entry), I still get the error listed
below, however the database connections will
Mark,
I am using the
'com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource'
class, which worked fine in 5.0. I've done some
further debugging and figured out a way to get the
datasource to at least run. If I explicitly pass the
"user" and "password" parameters (along with
"serverName", "data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom O'Neil wrote:
> I've been running an application on WebSphere 5.0
> (Linux) that uses the MySql Connector/J 3.10 to
> connect to a MySql-max 4.0.15 database (also on
> Linux). All was working fine, until I recently
> installed WebSphere 5.1. Now m
I've been running an application on WebSphere 5.0
(Linux) that uses the MySql Connector/J 3.10 to
connect to a MySql-max 4.0.15 database (also on
Linux). All was working fine, until I recently
installed WebSphere 5.1. Now my datasources
(configured exactly as before) no longer work -
WebSphere seem
