|
| Hi, we have an application which uses a datasource defined on a oracle jdbc driver. we have 2 different oracle jdbc drivers installed on the same node (versions 9 and 10g). The datasource for our application is defined with the version 10 driver, but the
application is picking the version 9 driver (it writes on the stdout its version). we have double checked the contents of the application, no ojdbc14.jar or com.oracle.* classes inside jars. We have put verbose classloading, and when the driver classes lo
ad, the classloader does not log the "from <file>" clause JUST for the oracle driver classes (any other classes are like:
[Loaded <class> from <file>]
For oracle classes:
[Loaded <class>]
So I don't have the certainty of where is "some" classloader finding the class. Printing the classpath does not give any ojdbc14.jar, so I guess a higher-level classloader is resolving the reference. I'm no expert on classloaders, so I wonder:
a) why the application is loading the wrong driver, if the datasource is declared for the right one.
b) how to guess the physical location (path and jar file) of the driver being used.
c) how to force the AS ( or the application ) to use these other drivers.
d) how to know the full "map" of jar files available in the classpath.
Notes:
- jdbc drivers are declared with NODE scope. There are NO drivers declared at another scope (AS, CELL).
- We cannot suppress the old driver because it's being used by other applications on the same node.
Please show your expertise with this victim of the classloader hell! Thank you very much in advance.
|
|