Marking this bug for 1.3

classloading is done using SolrCore#getResourceLoader()#findClass(name)

Using SolrResourceLoader#findClass does not solve the problem. From the official documentation at http://java.sun.com/j2se/1.5.0/docs/guide/jdbc/getstart/drivermanager.html

For security reasons, the JDBC management layer will keep track of which class loader provided which driver. Then when the DriverManager class is opening a connection, it will use only drivers that come from the local file system or from the same class loader as the code issuing the request for a connection.

Since the loading is done by SolrResourceLoader using a different class loader and the call to DriverManager.getConnection is made from a different one, a SQLException is thrown – "java.sql.SQLException: No suitable driver".

A hackish work around to the class loader issue.

This patch tries to use SolrResourceLoader#findClass to load the Driver class. It tries to use DriverManager#getConnection. If that fails, we try to instantiate the Driver class and use the Driver#connect method directly bypassing the DriverManager. This workaround is documented in the JdbcDataSource class.

I will commit this shortly.

Committed revision 690131.

Thanks Walter and Noble!