Can you figure out why a different classloader is used if you can debug
into the code?
Shaun
Philipp Kursawe wrote:
On Tue,
07 Apr 2009 20:52:47 +0200, Shaun Smith <shaun.smith@xxxxxxxxxx>
wrote:
I'm not sure how you get variable behavior
from the code since the code
path is always the same, however you can also get a "no suitable
driver"
when you do actually find the driver but the database connection
doesn't
work. This is definitely misleading but I have seen it happen when I
haven't started Oracle XE and attempt to run a program. Are you sure
that your database is always available? Perhaps you're out of
connections when you attempt to connect sometimes?
No, the database is running in a VM on my local machine. The connection
is not the problem. I can debug into the code and its a classloader
issue.
The connection to the database is fine.
Phil
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
--
Shaun Smith | Principal Product Manager
Phone: ++19055023094 | |
Oracle Oracle Server Technologies, Oracle
TopLink
ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga,
Ontario | L5R 3P4
Oracle is committed to developing practices and products that
help protect the environment
|
