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: [EMAIL PROTECTED] Web: www.gmfoto.de David Jencks <[EMAIL PROTECTED]> 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, [EMAIL PROTECTED] wrote: > > > > > Hi Lin, > > > > thanx for givin pervasive a chance to survive ;-) > > > > "Lin Sun" <[EMAIL PROTECTED]> 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 > > > > <?xml version="1.0" encoding="UTF-8"?> > > <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/ > > connector-1.2"> > > <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/ > deployment-1.2 > > "> > > <dep:moduleId> > > <dep:groupId>console.dbpool</dep:groupId> > > <dep:artifactId>jdbc%2Frational</dep:artifactId> > > <dep:version>1.0</dep:version> > > <dep:type>rar</dep:type> > > </dep:moduleId> > > <dep:dependencies> > > <dep:dependency> > > <dep:groupId>com.pervasive.jdbc.v2</dep:groupId> > > <dep:artifactId>jpscs</dep:artifactId> > > <dep:version>1</dep:version> > > <dep:type>jar</dep:type> > > </dep:dependency> > > <dep:dependency> > > <dep:groupId>com.pervasive.jdbc.v2</dep:groupId> > > <dep:artifactId>pvjdbc2</dep:artifactId> > > <dep:version>1</dep:version> > > <dep:type>jar</dep:type> > > </dep:dependency> > > <dep:dependency> > > <dep:groupId>com.pervasive.jdbc.v2</dep:groupId> > > <dep:artifactId>pvjdbc2x</dep:artifactId> > > <dep:version>1</dep:version> > > <dep:type>jar</dep:type> > > </dep:dependency> > > </dep:dependencies> > > </dep:environment> > > <resourceadapter> > > <outbound-resourceadapter> > > <connection-definition> > > <connectionfactory-interface>javax.sql.DataSource</ > > connectionfactory-interface> > > <connectiondefinition-instance> > > <name>jdbc/rational</name> > > <config-property-setting > > name="Driver">com.pervasive.jdbc.v2.Driver</config-property-setting> > > <config-property-setting > > name="ConnectionURL">jdbc:pervasive://srv-vm-w2k3-rat.gmfoto.de/ > > RATIONAL</config-property-setting> > > <connectionmanager> > > <local-transaction/> > > <single-pool> > > <max-size>10</max-size> > > <min-size>0</min-size> > > <match-one/> > > </single-pool> > > </connectionmanager> > > </connectiondefinition-instance> > > </connection-definition> > > </outbound-resourceadapter> > > </resourceadapter> > > </connector> > > > > --- snip > > > > > > Thx for your help > > > > > > GM-Foto GmbH > > Thomas Poth > > > > IT-Manager > > Tel.: 0049-69-238570-0 > > Fax: 0049-69-238570-30 > > Mail: [EMAIL PROTECTED] > > Web: www.gmfoto.de > > > > > > > > > -------------------------------------------------------------------------------------------------------------- > > GM-Foto GmbH, Taunusstraße 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äftsführer: Walter Adler und Harald Remsperger > > > > Öffnungszeiten: Montag - Freitag, 9:00 - 18:30 Uhr > > > > Internet: http://www.gmfoto.de , E-Mail: [EMAIL PROTECTED] > > > -------------------------------------------------------------------------------------------------------------- > -------------------------------------------------------------------------------------------------------------- GM-Foto GmbH, Taunusstraße 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äftsführer: Walter Adler und Harald Remsperger Öffnungszeiten: Montag - Freitag, 9:00 - 18:30 Uhr Internet: http://www.gmfoto.de , E-Mail: [EMAIL PROTECTED] --------------------------------------------------------------------------------------------------------------
