Ojdbc6 driver does not work with hibernate 3 and c3p0

Question

Hi,
I am trying to connect to the 11g database through hibernate and c3p0. When I use ojdbc14 as my driver, it is connecting properly. But when I try using ojdbc6, it is failing saying Invalid username password, even though I specify the correct credentials. Can you please help me with this?
12:04:05,411 DEBUG [com.mchange.v2.resourcepool.BasicResourcePool] awaitAvailable(): [unknown]
12:04:05,411 DEBUG [com.mchange.v2.resourcepool.BasicResourcePool] trace com.mchange.v2.resourcepool.BasicResourcePool@23000bcf [managed: 0, unused: 0, excluded: 0]
com.mchange.v2.resourcepool.BasicResourcePool An exception occurred while acquiring a resource.java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Thanks in advance!

Answer 1

I don't know what your problem actually was. I do know that I have had problems with putting jars into the extensions directory. And those problems were because the extensions directory isn't precisely "part of the classpath". (Regardless of careless people who say "Put X into the extensions directory because it's part of your classpath.")
Classes in the extensions directory are loaded by a classloader which doesn't have access to anything which is in the real classpath. Normally that isn't a problem for things like JDBC drivers, but for things which you expect to work with classes you put in the classpath, they fail because they can't load classes from the classpath.
So I don't see why a JDBC driver should have that kind of problem, especially with getting authentication parameters. I would think that Hibernate (which is in your classpath, right?) could talk to the JDBC driver in the extensions directory with no problem. One possibility is that you put it in the extensions directory for some other JRE than the one you were using to run your application, but that's just speculation. I don't really have any idea.