If there is a wrong service entry then the DriverManager can't init and the method getConnection() does not work (see stacktrace below). A wrong entry should be skip. If an error message is print then is should also include the jar file where the entry is loaded.
 
We have switch a large application from JDK 1.5 to JDK 1.6 and it does not work and the follow exception occur. We have search in over 100 jar files. The problem was a mistake in a cvs and a build script.
 

 
 
sun.misc.ServiceConfigurationError: java.sql.Driver: Provider com.inet.pool.PoolDriver not found
 at sun.misc.Service.fail(Unknown Source)
 at sun.misc.Service.access$000(Unknown Source)
 at sun.misc.Service$LazyIterator.next(Unknown Source)
 at java.sql.DriverManager.loadInitialDrivers(Unknown Source)
 at java.sql.DriverManager.initialize(Unknown Source)
 at java.sql.DriverManager.getDriver(Unknown Source)