1 of 1 people found this helpful
Do you have another *-ds.xml file that define an Oracle data source? If so, all it takes is one to load the proper driver class, then when the URL is passed to the driver manager and it polls the driver classes, the Oracle driver will claim the URL.
Thanks for getting back to me Peter,
Sorry about the delay in my response, it has been one of those weeks. I've just removed all other datasources from my file and the same issue still seems to be occurring.
I've also searched through my jboss configuration and can't find a mention of 'OracleDriver'
Then there must be some code somewhere that is loading the Oracle driver class. If you add "-verbose:class" to the JVM options in the run script, the JVM will print out the classes loaded and the JAR file each one came from. With this setting you should be able to see the driver being loaded at some point; unfortunately that will not help you identify what is loading the driver.
Just had another thought - look in the jmx console at what data sources are registered. Of course, this won't list cases where code is loading the driver.