Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 10708 invoked from network); 31 Jul 2008 14:02:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jul 2008 14:02:40 -0000 Received: (qmail 30662 invoked by uid 500); 31 Jul 2008 14:02:37 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 30631 invoked by uid 500); 31 Jul 2008 14:02:37 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 30620 invoked by uid 99); 31 Jul 2008 14:02:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2008 07:02:37 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of linsun.unc@gmail.com designates 74.125.46.29 as permitted sender) Received: from [74.125.46.29] (HELO yw-out-2324.google.com) (74.125.46.29) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2008 14:01:41 +0000 Received: by yw-out-2324.google.com with SMTP id 2so284062ywt.85 for ; Thu, 31 Jul 2008 07:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tjs01GJ2BQ5g5RroaU4GWQVQJkQrScGm9qYFYVvZW+M=; b=dglEoaQsdRd8p4JalckAIIvmuCYn2RmD/hoX7QEwWm+wxC8k5AOf/aVb/xy3uYeFBs /iqaSM03LqOpr8v9VGV6zml5woELLNYrH8cBp9nuj0wUZopOOy257J2D36H28B+b2Ymj 1sCAFgPIpmNgkrtYKqC300mUaewCzBZReV084= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CwBW7kBvxJsvPG1qmEXiNko2RDdruv1T37TnDtjCjkzO9fTybAhXo3LXMfmn2aAIRq U/wnzvt/s9mO9gViVLxR8iz9/8Taq9UmXs77zDWOpmFGnqtr1t7wNlX5DfYgYxCa8N4B fnHfhnqfSS3NwCWSXAKDvBsdiuhLCJdia55DQ= Received: by 10.151.143.3 with SMTP id v3mr1290083ybn.229.1217512926588; Thu, 31 Jul 2008 07:02:06 -0700 (PDT) Received: by 10.150.137.19 with HTTP; Thu, 31 Jul 2008 07:02:06 -0700 (PDT) Message-ID: Date: Thu, 31 Jul 2008 10:02:06 -0400 From: "Lin Sun" To: user@geronimo.apache.org Subject: Re: Re: Antwort: Re: Problems Connecting to Pervasive SQL Database In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <001a01c8ec85$17c8cbe0$a20a0a0a@TOMMYT60p> <1F6C2968-4F18-4D38-81F9-E77F7B908F6E@yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, Thanks for the feedback. You are right, the prob is the artifact name - jdbc%2Frational which has a / in it. I thought this was a known prob for db pool created from admin console, but I cannot find a JIRA about it. I'll keep looking. Lin On Thu, Jul 31, 2008 at 9:22 AM, wrote: > > Hi David, > Hi Lin, > > i tried another Poolname and it worked for me. > > The port must not be assigned in the connection url it works fine without= . > > But if a took the Poolname jdbc/rational it fails. > If i took the Poolname rational it's fine. > > I hope this is usefull. > > THX for your help on this case. > > Best regards > > GM-Foto GmbH > Thomas Poth > > IT-Manager > Tel.: 0049-69-238570-0 > Fax: 0049-69-238570-30 > Mail: poth@gmfoto.de > Web: > www.gmfoto.de > > > > David Jencks schrieb am 23.07.2008 19:11:01: > >> [Bild entfernt] >> >> Re: Antwort: Re: Problems Connecting to Pervasive SQL Database >> >> David Jencks >> >> an: >> >> user >> >> 23.07.2008 19:12 >> >> Bitte Antwort an user >> >> Your plan looks ok to me. The missing class is from the tranql >> connector, not pervasive. It's supposed to be in a jar unpacked from >> the tranql rar into your connector deployment. Could you look around >> inside console/dbpool/jdbc%2Frational/1.0/rar and see what's there? >> >> Depending on how successful we are at cleaning up after deployment >> failures you might need to save the plan and deploy using "deploy new" >> without trying to start the connector. >> >> thanks >> david jencks >> >> On Jul 23, 2008, at 9:30 AM, tpoth@gmfoto.de wrote: >> >> > >> > Hi Lin, >> > >> > thanx for givin pervasive a chance to survive ;-) >> > >> > "Lin Sun" schrieb am 23.07.2008 17:45:09: >> > >> > > I don't remember seeing anyone configure G w/ pervasive SQL database >> > > server... >> > >> > I'm not very lucky about it, but our ERP Software bases on this >> > Database. >> > And i had to get the data out of it for our E-Commerce Site. >> > >> > > The error looks like the connector failed to load the jdbc drivers. >> > > Here are some things I can think of - >> > > >> > > - After you upload these files via admin console, what does these >> > file >> > > look like in the repository? They should be located somewhere under >> > > geronimo_home/repository/com/pervasive/jdbc/ >> > > I don't know if the admin console would convert these jars to a >> > maven2 >> > > recognizable format (such as name-version.jar, for example >> > > sqljdbc-1.1.jar). >> > >> > It semms that this is OK >> > >> > The Files are organized as follows: >> > geronimo_home/repository/com/pervasive/jdbc/v2/jpscs/1/jpscs-1.jar >> > geronimo_home/repository/com/pervasive/jdbc/v2/pvjdbc2/1/pvjdbc2-1.jar >> > geronimo_home/repository/com/pervasive/jdbc/v2/pvjdbc2x/1/ >> > pvjdbcv2x-1.jar >> > >> > > - When you create a db pool via admin console, make sure you pick >> > the >> > > jars you installed onto the repository as dependencies. >> > >> > I'm sure to do so. >> > >> > > - If you still fail to deploy the pool, can you use the show plan >> > > button before deploying the pool to show us the plan? >> > > >> > >> > Here is the Deployment Plan: >> > >> > --- snip >> > >> > >> > > > connector-1.2"> >> > > deployment-1.2 >> > "> >> > >> > console.dbpool >> > jdbc%2Frational >> > 1.0 >> > rar >> > >> > >> > >> > com.pervasive.jdbc.v2 >> > jpscs >> > 1 >> > jar >> > >> > >> > com.pervasive.jdbc.v2 >> > pvjdbc2 >> > 1 >> > jar >> > >> > >> > com.pervasive.jdbc.v2 >> > pvjdbc2x >> > 1 >> > jar >> > >> > >> > >> > >> > >> > >> > javax.sql.DataSource> > connectionfactory-interface> >> > >> > jdbc/rational >> > > > name=3D"Driver">com.pervasive.jdbc.v2.Driver >> > > > name=3D"ConnectionURL">jdbc:pervasive://srv-vm-w2k3-rat.gmfoto.de/ >> > RATIONAL >> > >> > >> > >> > 10 >> > 0 >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > --- snip >> > >> > >> > Thx for your help >> > >> > >> > GM-Foto GmbH >> > Thomas Poth >> > >> > IT-Manager >> > Tel.: 0049-69-238570-0 >> > Fax: 0049-69-238570-30 >> > Mail: poth@gmfoto.de >> > Web: www.gmfoto.de >> > >> > >> > >> > >> >> ------------------------------------------------------------------------= -------------------------------------- >> > GM-Foto GmbH, Taunusstra=DFe 47, D-60329 Frankfurt am Main >> > Telefon: +49 69 238570-0, Telefax: +49 69 238570-30 >> > Eingetragen beim Amtsgericht Frankfurt am Main: HRB 19494 >> > Gesch=E4ftsf=FChrer: Walter Adler und Harald Remsperger >> > >> > =D6ffnungszeiten: Montag - Freitag, 9:00 - 18:30 Uhr >> > >> > Internet: http://www.gmfoto.de , E-Mail: gmfoto@gmfoto.de >> > >> >> ------------------------------------------------------------------------= -------------------------------------- >> > > > -------------------------------------------------------------------------= ------------------------------------- > GM-Foto GmbH, Taunusstra=DFe 47, D-60329 Frankfurt am Main > Telefon: +49 69 238570-0, Telefax: +49 69 238570-30 > Eingetragen beim Amtsgericht Frankfurt am Main: HRB 19494 > Gesch=E4ftsf=FChrer: Walter Adler und Harald Remsperger > > =D6ffnungszeiten: Montag - Freitag, 9:00 - 18:30 Uhr > > Internet: http://www.gmfoto.de , E-Mail: gmfoto@gmfoto.de > -------------------------------------------------------------------------= -------------------------------------