JDBC 驅動加載過程

參見如下簡單的程序

package db;

import java.sql.*;

public class DBTest {
    private static final String USERNAME = "root";
    private static final String PASSWD = "root";
    private static final String DATABASE = "test";
    private static final String DBMS = "mysql";
    private static final String HOST = "localhost";
    private static final String PORT = "3306";
    private static final String DSN = "jdbc:" + DBMS + "://" + HOST + ":" + PORT + "/" + DATABASE;

    public static void main(String[] args) {
        try {
            Connection conn = DriverManager.getConnection(DSN, USERNAME, PASSWD);
            String query = "SELECT * FROM user";
            Statement stmt = conn.createStatement();
            ResultSet rs = stmt.executeQuery(query);
            while (rs.next()) {
                System.out.println(rs.getInt(1) + " " + rs.getString(2) + " " + rs.getInt(3));
            }
        } catch (SQLException e) {
            e.printStackTrace();
        }
    }
}

下面我們來分析 DriverManager 的這個方法：

public static Connection getConnection(String url,
                       String user,
                       String password)
                                throws SQLException

查看一下DriverManager源碼，代碼塊我按執行步驟全部貼出來：

1. 調用getConnection()方法

    /**
     * Attempts to establish a connection to the given database URL.
     * The <code>DriverManager</code> attempts to select an appropriate driver from
     * the set of registered JDBC drivers.
     *
     * @param url a database url of the form 
     * <code>jdbc:<em>subprotocol</em>:<em>subname</em></code>
     * @param user the database user on whose behalf the connection is being
     *   made
     * @param password the user's password
     * @return a connection to the URL 
     * @exception SQLException if a database access error occurs
     */
    public static Connection getConnection(String url, 
    String user, String password) throws SQLException {
        java.util.Properties info = new java.util.Properties();

        // Gets the classloader of the code that called this method, may 
    // be null.
    ClassLoader callerCL = DriverManager.getCallerClassLoader();

    if (user != null) {
        info.put("user", user);
    }
    if (password != null) {
        info.put("password", password);
    }

        return (getConnection(url, info, callerCL));
    }

 

 

2. 調用實際起作用的getConnection()方法

//  Worker method called by the public getConnection() methods.
    private static Connection getConnection(
    String url, java.util.Properties info, ClassLoader callerCL) throws SQLException {
    java.util.Vector drivers = null;
        /*
     * When callerCl is null, we should check the application's
     * (which is invoking this class indirectly)
     * classloader, so that the JDBC driver class outside rt.jar
     * can be loaded from here.
     */
    synchronized(DriverManager.class) {  
      // synchronize loading of the correct classloader.
      if(callerCL == null) {
          callerCL = Thread.currentThread().getContextClassLoader();
       }    
    } 
     
    if(url == null) {
        throw new SQLException("The url cannot be null", "08001");
    }
    
    println("DriverManager.getConnection(\"" + url + "\")");
    
    if (!initialized) {
        initialize();
    }

    synchronized (DriverManager.class){ 
            // use the readcopy of drivers
        drivers = readDrivers;  
        }

    // Walk through the loaded drivers attempting to make a connection.
    // Remember the first exception that gets raised so we can reraise it.
    SQLException reason = null;
    for (int i = 0; i < drivers.size(); i++) {
        DriverInfo di = (DriverInfo)drivers.elementAt(i);
      
        // If the caller does not have permission to load the driver then 
        // skip it.
        if ( getCallerClass(callerCL, di.driverClassName ) != di.driverClass ) {
        println("    skipping: " + di);
        continue;
        }
        try {
        println("    trying " + di);
        Connection result = di.driver.connect(url, info);
        if (result != null) {
            // Success!
            println("getConnection returning " + di);
            return (result);
        }
        } catch (SQLException ex) {
        if (reason == null) {
            reason = ex;
        }
        }
    }
    
    // if we got here nobody could connect.
    if (reason != null)    {
        println("getConnection failed: " + reason);
        throw reason;
    }
    
    println("getConnection: no suitable driver found for "+ url);
    throw new SQLException("No suitable driver found for "+ url, "08001");
    }

 這里有幾個比較重要的地方，一個L25的initialize()方法，下面是他的源碼

// Class initialization.
    static void initialize() {
        if (initialized) {
            return;
        }
        initialized = true;
        loadInitialDrivers();
        println("JDBC DriverManager initialized");
    }

private static void loadInitialDrivers() {
        String drivers;
    
        try {
        drivers = (String) java.security.AccessController.doPrivileged(
        new sun.security.action.GetPropertyAction("jdbc.drivers"));
        } catch (Exception ex) {
            drivers = null;
        }
        
        // If the driver is packaged as a Service Provider,
        // load it.
        
        // Get all the drivers through the classloader 
        // exposed as a java.sql.Driver.class service.
    
     DriverService ds = new DriverService();

     // Have all the privileges to get all the 
     // implementation of java.sql.Driver
     java.security.AccessController.doPrivileged(ds);       
            
        println("DriverManager.initialize: jdbc.drivers = " + drivers);
        if (drivers == null) {
            return;
        }
        while (drivers.length() != 0) {
            int x = drivers.indexOf(':');
            String driver;
            if (x < 0) {
                driver = drivers;
                drivers = "";
            } else {
                driver = drivers.substring(0, x);
                drivers = drivers.substring(x+1);
            }
            if (driver.length() == 0) {
                continue;
            }
            try {
                println("DriverManager.Initialize: loading " + driver);
                Class.forName(driver, true,
                  ClassLoader.getSystemClassLoader());
            } catch (Exception ex) {
                println("DriverManager.Initialize: load failed: " + ex);
            }
        }
    }

這一段就是加載數據庫驅動的地方，以我用的connector/j為例，看L27，這個DriverService是一個內部類，代碼如下：

// DriverService is a package-private support class.    
class DriverService implements java.security.PrivilegedAction {
        Iterator ps = null;
    public DriverService() {};
        public Object run() {

    // uncomment the followin line before mustang integration   
        // Service s = Service.lookup(java.sql.Driver.class);
    // ps = s.iterator();

    ps = Service.providers(java.sql.Driver.class);

    /* Load these drivers, so that they can be instantiated. 
     * It may be the case that the driver class may not be there
         * i.e. there may be a packaged driver with the service class
         * as implementation of java.sql.Driver but the actual class
         * may be missing. In that case a sun.misc.ServiceConfigurationError
         * will be thrown at runtime by the VM trying to locate 
     * and load the service.
         * 
     * Adding a try catch block to catch those runtime errors
         * if driver not available in classpath but it's 
     * packaged as service and that service is there in classpath.
     */
        
    try {
           while (ps.hasNext()) {
               ps.next();
           } // end while
    } catch(Throwable t) {
        // Do nothing
    }
        return null;
    } //end run

} //end DriverService

L11的 sun.misc.Service.providers()方法是關鍵所在，代碼如下

    /**
     * Locates and incrementally instantiates the available providers of a
     * given service using the given class loader.
     *
     * <p> This method transforms the name of the given service class into a
     * provider-configuration filename as described above and then uses the
     * <tt>getResources</tt> method of the given class loader to find all
     * available files with that name.  These files are then read and parsed to
     * produce a list of provider-class names.  The iterator that is returned
     * uses the given class loader to lookup and then instantiate each element
     * of the list.
     *
     * <p> Because it is possible for extensions to be installed into a running
     * Java virtual machine, this method may return different results each time
     * it is invoked. <p>
     *
     * @param  service
     *         The service's abstract service class
     *
     * @param  loader
     *         The class loader to be used to load provider-configuration files
     *         and instantiate provider classes, or <tt>null</tt> if the system
     *         class loader (or, failing that the bootstrap class loader) is to
     *         be used
     * 
     * @return An <tt>Iterator</tt> that yields provider objects for the given
     *         service, in some arbitrary order.  The iterator will throw a
     *         <tt>ServiceConfigurationError</tt> if a provider-configuration
     *         file violates the specified format or if a provider class cannot
     *         be found and instantiated.
     *
     * @throws ServiceConfigurationError
     *         If a provider-configuration file violates the specified format
     *         or names a provider class that cannot be found and instantiated
     *
     * @see #providers(java.lang.Class)
     * @see #installedProviders(java.lang.Class)
     */
    public static Iterator providers(Class service, ClassLoader loader)
    throws ServiceConfigurationError
    {
    return new LazyIterator(service, loader);
    }

/**
     * Private inner class implementing fully-lazy provider lookup
     */
    private static class LazyIterator implements Iterator {

    Class service;
    ClassLoader loader;
    Enumeration configs = null;
    Iterator pending = null;
    Set returned = new TreeSet();
    String nextName = null;

    private LazyIterator(Class service, ClassLoader loader) {
        this.service = service;
        this.loader = loader;
    }

    public boolean hasNext() throws ServiceConfigurationError {
        if (nextName != null) {
        return true;
        }
        if (configs == null) {
        try {
            String fullName = prefix + service.getName();
            if (loader == null)
            configs = ClassLoader.getSystemResources(fullName);
            else
            configs = loader.getResources(fullName);
        } catch (IOException x) {
            fail(service, ": " + x);
        }
        }
        while ((pending == null) || !pending.hasNext()) {
        if (!configs.hasMoreElements()) {
            return false;
        }
        pending = parse(service, (URL)configs.nextElement(), returned);
        }
        nextName = (String)pending.next();
        return true;
    }

    public Object next() throws ServiceConfigurationError {
        if (!hasNext()) {
        throw new NoSuchElementException();
        }
        String cn = nextName;
        nextName = null;
        try {
        return Class.forName(cn, true, loader).newInstance();
        } catch (ClassNotFoundException x) {
        fail(service,
             "Provider " + cn + " not found");
        } catch (Exception x) {
        fail(service,
             "Provider " + cn + " could not be instantiated: " + x,
             x);
        }
        return null;    /* This cannot happen */
    }

    public void remove() {
        throw new UnsupportedOperationException();
    }

    }

好了。經過各種進入，終於到達了目的地，上面這段代碼就是加載數據庫驅動的所在，請看LazyIterator里的從L57開始的這一段

實際上很簡單，他就是去CLASSPATH里的library里找  META-INF/services/java.sql.Driver 這個文件，其中 java.sql.Driver 這個名字是通過上面的 service.getName()獲得的。 數據庫驅動的類里都會有 META-INF 這個文件夾，我們可以MySQL的connector/j數據庫驅動加到環境變量里后自己嘗試一下輸出，代碼如下

package test;

import java.io.IOException;
import java.net.URL;
import java.sql.Driver;
import java.util.Enumeration;

public class Test {
    public static void main(String[] args) throws IOException {
        Enumeration<URL> list = ClassLoader.getSystemResources("META-INF/services/" + Driver.class.getName());
        while (list.hasMoreElements()) {
            System.out.println(list.nextElement());
        }
    }
}

控制台會輸出

jar:file:/usr/local/glassfish3/jdk7/jre/lib/resources.jar!/META-INF/services/java.sql.Driver
jar:file:/home/alexis/mysql-connector/mysql-connector-java-5.1.22-bin.jar!/META-INF/services/java.sql.Driver

看到了嗎，這兩個jar文件一個是jdk自帶的，另一個是我們自己加到環境變量里的mysql驅動，然后我們再看看這兩個java.sql.Driver里的東西，他們分別是

sun.jdbc.odbc.JdbcOdbcDriver
com.mysql.jdbc.Driver

自此，我們終於找到了我們需要加載的兩個數據庫驅動類的名稱。然后再看LazyItarator里的next方法，注意到里面的forName了吧，這個方法就是加載類信息。順便提一下，實際上forName方法里也是調用的ClassLoader的loadClass()方法來加載類信息的。

這里還有一步很關鍵的，就是加載類信息的時候發生了什么。我們看看 com.mysql.jdbc.Driver 的源碼

public class Driver extends NonRegisteringDriver implements java.sql.Driver {
    // ~ Static fields/initializers
    // ---------------------------------------------

    //
    // Register ourselves with the DriverManager
    //
    static {
        try {
            java.sql.DriverManager.registerDriver(new Driver());
        } catch (SQLException E) {
            throw new RuntimeException("Can't register driver!");
        }
    }

    // ~ Constructors
    // -----------------------------------------------------------

    /**
     * Construct a new driver and register it with DriverManager
     * 
     * @throws SQLException
     *             if a database error occurs.
     */
    public Driver() throws SQLException {
        // Required for Class.forName().newInstance()
    }
}

注意到這個static語句塊了吧。就是這段代碼，把自己注冊到了DriverManager的driverlist里。

終於結束了，當所有驅動程序的Driver實例注冊完畢，DriverManager就開始遍歷這些注冊好的驅動，對傳入的數據庫鏈接DSN調用這些驅動的connect方法，最后返回一個對應的數據庫驅動類里的connect方法返回的java.sql.Connection實例，也就是我最開始那段測試代碼里的conn。大家可以返回去看看DriverManager在initialize()結束后干了什么就明白

 

最后總結一下流程：

1. 調用 getConnection 方法

2. DriverManager 通過  SystemProerty jdbc.driver 獲取數據庫驅動類名

或者

通過ClassLoader.getSystemResources 去CLASSPATH里的類信息里查找 META-INF/services/java.sql.Driver 這個文件里查找獲取數據庫驅動名

3. 通過找的的driver名對他們進行類加載

4. Driver類在被加載的時候執行static語句塊，將自己注冊到DriverManager里去

5. 注冊完畢后 DriverManager 調用這些驅動的connect方法，將合適的Connection 返回給客戶端