From users-return-6277-apmail-continuum-users-archive=continuum.apache.org@continuum.apache.org Tue Apr 01 09:51:58 2008 Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 71021 invoked from network); 1 Apr 2008 09:51:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 09:51:58 -0000 Received: (qmail 78171 invoked by uid 500); 1 Apr 2008 09:51:57 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 78135 invoked by uid 500); 1 Apr 2008 09:51:57 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 78126 invoked by uid 99); 1 Apr 2008 09:51:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 02:51:57 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.127.3.27] (HELO mail07.allianz.de) (194.127.3.27) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 09:51:06 +0000 Received: from naimuckl.allianzde.rootdom.net (naimuckl.allianzde.rootdom.net [10.99.150.64] (may be forged)) by mail07.allianz.de with ESMTP id m319pNJI006999 for ; Tue, 1 Apr 2008 11:51:26 +0200 (MEST) Received: from naimuck6.allianzde.rootdom.net ([10.99.150.41]) by naimuckl.allianzde.rootdom.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Apr 2008 11:51:25 +0200 Received: from naimuco3.allianzde.rootdom.net ([10.99.129.58]) by naimuck6.allianzde.rootdom.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Apr 2008 11:51:24 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: AW: using Derby network-server instead of Embedded-driver Date: Tue, 1 Apr 2008 11:51:24 +0200 Message-ID: <7ACB14CE427DB540A30E985A4E5FF57B04C9B126@naimuco3.allianzde.rootdom.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: using Derby network-server instead of Embedded-driver Thread-Index: AciT1MYy66fFwx1JQT6IKH6fX332vQACQIEg From: "Lustig, Marc (Allianz Deutschland AG)" To: X-OriginalArrivalTime: 01 Apr 2008 09:51:24.0898 (UTC) FILETIME=[F2B3BC20:01C893DD] X-Virus-Checked: Checked by ClamAV on apache.org I just found out it's possible to connect to the database using embedded = driver when continuum is stopped. Problem solved. -----Urspr=FCngliche Nachricht----- Von: Lustig, Marc (Allianz Deutschland AG)=20 Gesendet: Dienstag, 1. April 2008 10:46 An: 'users@continuum.apache.org' Betreff: using Derby network-server instead of Embedded-driver In order to migrate the data into mysql we need to connect to the = derby-database of the old installation. By default the embedded driver is used, hence it's impossible to connect = to this database (I least I didn't find a way).=20 I have read in the list-archive that it's possible to use the derby = network-driver instead of the embedded driver. That way it is possible = to create a connection from another JVM to connect to the continuum = derby database. What needs to be configured to replace the embedded driver with the = network driver?