Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 61201 invoked from network); 1 Jun 2005 20:44:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jun 2005 20:44:13 -0000 Received: (qmail 10373 invoked by uid 500); 1 Jun 2005 20:44:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 10338 invoked by uid 500); 1 Jun 2005 20:44:11 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 10324 invoked by uid 99); 1 Jun 2005 20:44:11 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 01 Jun 2005 13:44:07 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 0FA10187 for ; Wed, 1 Jun 2005 22:43:53 +0200 (CEST) Message-ID: <1653675938.1117658633062.JavaMail.jira@ajax.apache.org> Date: Wed, 1 Jun 2005 22:43:53 +0200 (CEST) From: "Samuel Andrew McIntyre (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-93) Cannot connect to Derby using DB2 Universal Driver In-Reply-To: <1605884250.1102439230005.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-93?page=all ] Samuel Andrew McIntyre resolved DERBY-93: ----------------------------------------- Resolution: Duplicate Duplicate of DERBY-92 > Cannot connect to Derby using DB2 Universal Driver > -------------------------------------------------- > > Key: DERBY-93 > URL: http://issues.apache.org/jira/browse/DERBY-93 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.0.2.1 > Environment: JDK 1.4.2.x > Reporter: Raj Subramani > Priority: Minor > > As per the Server & Admi guide, the Derby network server should be accesible using the DB2 Universal Driver. > namely, > db2jcc.jar > db2jcc_license_c.jar > I have a (licensed) copy of the above driver which which I am able to connect to Cloudscape-DB2 v5.1.2. > Howver using the same driver jars I am unable to connect to Derby, the trace as follows: > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getConnection(DriverManager.java:532) > at java.sql.DriverManager.getConnection(DriverManager.java:171) > at db.connection.TestConnection.setUp(TestConnection.java:34) > at junit.framework.TestCase.runBare(TestCase.java:125) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:421) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:305) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:186) > My connectivity properties are: > db.driver=com.ibm.db2.jcc.DB2Driver > db.url=jdbc:derby:net://localhost/:bootPassword= > db.user=demo > db.password=demo > The Derby database was created using ij and is an encrypted database. I am able to connect to Derby with the embedded driver > db.driver=db.driver=org.apache.derby.jdbc.EmbeddedDriver > db.url=jdbc:derby:H:/rl-hibernate/db/derby_10_0_2_1/;bootPassword= > db.user=demo > db.password=demo > NOTE: The use of the ";" for bootPassword in embedded mode and the use of ":" in the network mode. This is as per the docs (and I have even tried using ";" for the networked mode but it will still not connect). > I then went and downloaded Clodscape 10 and used > db2jcc.jar > db2jcc_license_c.jar > from this distribution. > When I used the ":" syntax for the bootpassword, as per the docs I got: > com.ibm.db2.jcc.c.SqlException: Invalid database url syntax: jdbc:derby:net://localhost/:bootPassword= > at com.ibm.db2.jcc.DB2Driver.tokenizeURLProperties(DB2Driver.java:555) > at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:131) > at java.sql.DriverManager.getConnection(DriverManager.java:512) > at java.sql.DriverManager.getConnection(DriverManager.java:171) > at db.connection.TestConnection.setUp(TestConnection.java:34) > at junit.framework.TestCase.runBare(TestCase.java:125) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:421) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:305) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:186) > However, using a ";" before bootPassword=... > results in a SUCCESSFUL connection. > I think it might be useful to state that it will work only with Cloudscape 10.0 (or above) IBM Universal drivers. > Also given that this licensed driver may expire after some time (as per the IBM license file), it makes it diffult to use this over a longer term. Will there be a AF licensed network driver for Derby? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira