Depends on the driver. If the IP connection is keep-alive, that probably explains it.

I may be wrong but the Java Object "java.sql.Connection" is being instanciated and implictly opening a connection to the datasource the first time through with the added the overhead of bring this object to life in the local runtime JVM which could account for the decrepancy you have described. IE. the implict ClassLoader function required for the first instance not required for the others, viewable by using verbose opton of the JRE executing test code if you want to parse through it.



To further invetigate you attempt the same test set using various accounts to the same database and then mixing the account used for illiteration one and subsequent connections to determine if the connecton time remains consistant under those circumstances.