I am working on an issue where two applications (one connecting to DB2 with JCC) and one using Derby are running in the same JVM. When using server side JDBC using DriverManager.getConnection("jdbc:default:connection"), the JCC driver, which is used for DB2 server side JDBC, accepts the url and tries to make a DB2 T2 connection. It seems valid for JCC, like the Derby embedded driver to accept this url. With multiple Drivers in the same JVM, how can DriverManager differentiate?

Thanks

Kathey

Reply via email to