Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 24095 invoked from network); 3 Apr 2008 16:16:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Apr 2008 16:16:52 -0000 Received: (qmail 36663 invoked by uid 500); 3 Apr 2008 16:16:49 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 36637 invoked by uid 500); 3 Apr 2008 16:16:49 -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 36626 invoked by uid 99); 3 Apr 2008 16:16:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 09:16:49 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hcunico@gmail.com designates 64.233.166.176 as permitted sender) Received: from [64.233.166.176] (HELO py-out-1112.google.com) (64.233.166.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 16:16:06 +0000 Received: by py-out-1112.google.com with SMTP id a25so3791156pyi.11 for ; Thu, 03 Apr 2008 09:16:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=2O3So7KoqZBDTlaPz3XvnT/F5xb57NxlX298ofi3blI=; b=oYfCx7ARijmye5M/CEeUKFCa2yUHgvyyhluTaNIJd1o3456F2QPh6EL8ItHKwxVpGNDntUyfTQbFIxsXAWmVPJUuHUcYsVVMgL/v6HxR6OiyBhcNCNiVDWwMcv/dAYXDOcoTaIjzhdCEuROojwP+4Wg+U48oN3VUghi0m7BcyUc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=SFFTnhvD7xOkvCzmFCrfXtHIwTpZR35kdk6txyvfDIliGVJ+yABlgF0QVSLhDoZsuWF20dGOeqAXQFFGCZuuHIT0YJqWtlpsV/s4Sa/B1M/yAdSqINd7V76NjijrzRy6XCD/lidGOhYvwR6pNIPF04OSY9RBo0ObxULGwb5Xgeg= Received: by 10.35.109.5 with SMTP id l5mr59136pym.5.1207239377828; Thu, 03 Apr 2008 09:16:17 -0700 (PDT) Received: from ?192.168.1.100? ( [71.70.229.168]) by mx.google.com with ESMTPS id a2sm3699965pyi.12.2008.04.03.09.16.16 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Apr 2008 09:16:17 -0700 (PDT) Message-ID: <47F502CE.1040104@gmail.com> Date: Thu, 03 Apr 2008 12:16:14 -0400 From: Hernan Cunico User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: user@geronimo.apache.org Subject: Re: Problem creating a DB2 datasource References: <16344329.post@talk.nabble.com> <22d56c4d0803272122tc868a97rc60911a892f2d77d@mail.gmail.com> <47ECE915.90500@apache.org> <16366049.post@talk.nabble.com> <825E7D34-2E7D-45AE-8922-B8A8DF54D6DE@yahoo.com> <47F10F32.9060706@gmail.com> <1644F9BA-BE9D-4CEF-8E9C-6100696AE494@yahoo.com> <47F12238.2080402@gmail.com> <47F4F236.7050507@earthlink.net> In-Reply-To: <47F4F236.7050507@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Close but not cigar yet ;-) I just tested tranql-connector-db2-xa-1.2-20080326.214959-2.rar and getting some weird behavior. With 1.2 snapshot I can use the wizard, create a plan and deploy the pool; all from the admin console but I fail to access the database defined in the pool. (for the record it deploys OK from the console) The weird thing is that if I use the wizard just to create a plan but then deploy it from the command line it also deploys OK but also I CAN access the DB. So, not sure what the deal is. Am I doing something while substituting the connectors? should I delete 1.1 from the repo? Cheers! Hernan Joe Bohn wrote: > Hernan, > > Did you get a chance to give the 1.2 version a shot and see if it fixed > your problem? I'm wondering if this is an issue for 2.1.1. Also, is > there a JIRA for this issue? > > Thanks, > Joe > > > > Hernan Cunico wrote: >> yup, using the 1.1 version available on G 2.1. I'll give 1.2 a shot >> >> Cheers! >> Hernan >> >> David Jencks wrote: >>> Is this with the snapshot db2 tranql adapter.. >>> >>> _http://snapshots.repository.codehaus.org/org/tranql/tranql-connector-db2-xa/1.2-SNAPSHOT/tranql-connector-db2-xa-1.2-20080326.214959-2.rar_ >>> >>> >>> >>> The released 1.1 version has a problem with setting the trace file >>> that might be related to this. >>> thanks >>> david jencks >>> >>> On Mar 31, 2008, at 9:20 AM, Hernan Cunico wrote: >>>> I found some issues as well while deploying a pool using the db2 >>>> specific connector although my testing was on G 2.1. I'll repeat >>>> these on 2.0.2 as soon as I can. >>>> >>>> If I use the "generic" tranql connector the pool deploys OK with the >>>> appropriate plan and I can access the DB via such pool. >>>> >>>> If I use the tranql-connector-db2-xa connector with the >>>> corresponding deployment plan it will deploy OK but it fail when >>>> accessing the DB, here is the exception: >>>> >>>> 11:00:33,781 ERROR [MCFConnectionInterceptor] Error occurred >>>> creating ManagedConnection for >>>> org.apache.geronimo.connector.outbound.ConnectionInfo@11dc32b >>>> javax.resource.spi.ResourceAdapterInternalException: Unable to >>>> obtain physical connection to com.ibm.db2.jcc.DB2XADataSource@15be8ff >>>> at >>>> org.tranql.connector.jdbc.AbstractXADataSourceMCF.getPhysicalConnection(AbstractXADataSourceMCF.java:76) >>>> >>>> at >>>> org.tranql.connector.db2.XAMCF.createManagedConnection(XAMCF.java:59) >>>> at >>>> org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) >>>> >>>> at >>>> org.apache.geronimo.connector.outbound.LocalXAResourceInsertionInterceptor.getConnection(LocalXAResourceInsertionInterceptor.java:41) >>>> >>>> at >>>> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:70) >>>> >>>> at >>>> org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) >>>> >>>> at >>>> org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) >>>> >>>> at >>>> org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:94) >>>> >>>> ... >>>> Caused by: com.ibm.db2.jcc.b.SqlException: >>>> [ibm][db2][jcc][10257][10960] Unable to open file . >>>> at com.ibm.db2.jcc.b.ch.a(ch.java:111) >>>> at >>>> com.ibm.db2.jcc.DB2BaseDataSource.computePrintWriter(DB2BaseDataSource.java:2900) >>>> >>>> at >>>> com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriter(DB2BaseDataSource.java:2812) >>>> >>>> at >>>> com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:2792) >>>> >>>> at >>>> com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:2756) >>>> >>>> at >>>> com.ibm.db2.jcc.DB2XADataSource.getXAConnection(DB2XADataSource.java:73) >>>> >>>> at >>>> org.tranql.connector.jdbc.AbstractXADataSourceMCF.getPhysicalConnection(AbstractXADataSourceMCF.java:74) >>>> >>>> ... 33 more >>>> com.ibm.db2.jcc.b.SqlException: [ibm][db2][jcc][10257][10960] Unable >>>> to open file . >>>> at com.ibm.db2.jcc.b.ch.a(ch.java:111) >>>> ... >>>> >>>> I created the deployment plan using the Geronimo database pool >>>> wizard after adding the 2 (db2jcc-9.1.2.jar and >>>> db2jcc_license_cu-9.1.2.jar) DB2 drivers to the repo. >>>> >>>> Cheers! >>>> Hernan >>>> >>>> >>>> David Jencks wrote: >>>>> I'm not sure where you got the prototype for your plan, but I doubt >>>>> it was the documentation you linked to, unless someone has >>>>> completely revised that documentation since your first post. Your >>>>> plan uses the geronimo 1.0 plan syntax which is incompatible with >>>>> geronimo 1.1 and later, whereas the plan in the docs looks up to date. >>>>> The easiest way to get a working plan is to use the admin console >>>>> wizard to generate it. I suggest using the wizard to generate the >>>>> plan and then deploying using the command line. This way you can >>>>> easily study and modify the plan as needed. >>>>> thanks >>>>> david jencks >>>>> On Mar 28, 2008, at 7:47 PM, SKService wrote: >>>>>> >>>>>> Thankyou for your fruitful reply. But still I'm stuck. >>>>>> First, I already have "tranql-connector-db2-xa-1.1" under the path >>>>>> "repository/org/tranql/tranql-connector-db2-xa/1.1/tranql-connector-db2-xa-1.1.rar" >>>>>> . But I'm confused in using it because I'm not sure where in the >>>>>> plan to add >>>>>> the deployment plan tag referred by you, >>>>>> >>>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"> >>>>>> org.tranql >>>>>> tranql-connector-db2-xa >>>>>> rar >>>>>> >>>>>> >>>>>> Second, I've tried after correcting the command parameter >>>>>> sequence. The >>>>>> corrected command (with my old setup) is, >>>>>> deploy --user system --password manager deploy >>>>>> ..\repository\org\tranql\tranql-connector-ra\1.4\tranql-connector-ra-1.4.rar >>>>>> >>>>>> Please take a look at the error pasted below, which also has the >>>>>> plan. and >>>>>> suggested whether my plan needs to be corrected. >>>>>> >>>>>> Appreciate your help. >>>>>> >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin>deploy --user system --password >>>>>> manager >>>>>> deploy >>>>>> ..\repository\org\tranql\tranql-connector-ra\1.4\tranql-connector-ra-1.4.rar >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin\db2-geronimo-plan.xml >>>>>> Using GERONIMO_BASE: C:\geronimo-tomcat6-jee5-2.0.2 >>>>>> Using GERONIMO_HOME: C:\geronimo-tomcat6-jee5-2.0.2 >>>>>> Using GERONIMO_TMPDIR: var\temp >>>>>> Using JRE_HOME: C:\Program Files\Java\jdk1.5.0_06\jre >>>>>> Error: Unable to distribute tranql-connector-ra-1.4.rar: >>>>>> org.apache.geronimo.common.DeploymentException: Could not parse >>>>>> module descriptor >>>>>> >>>>>> Could not parse module descriptor >>>>>> >>>>>> Invalid deployment descriptor: errors: >>>>>> >>>>>> >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin\db2-geronimo-plan.xml:2:1: >>>>>> error: >>>>>> cvc-complex-type.3.2.1: Attribute not allowed (no wildcards >>>>>> allowed): configId in element >>>>>> connector@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 >>>>>> >>>>>> >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin\db2-geronimo-plan.xml:15:3: >>>>>> error: cvc-complex-type.2.4a: Expected element >>>>>> >>>>>> 'resourceadapter@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> >>>>>> instead of >>>>>> 'dependency@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> here in element >>>>>> connector@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 >>>>>> >>>>>> >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin\db2-geronimo-plan.xml:19:3: >>>>>> error: cvc-complex-type.2.4a: Expected element >>>>>> >>>>>> 'resourceadapter@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> >>>>>> instead of >>>>>> 'dependency@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> here in element >>>>>> connector@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 >>>>>> >>>>>> >>>>>> C:\geronimo-tomcat6-jee5-2.0.2\bin\db2-geronimo-plan.xml:23:3: >>>>>> error: cvc-complex-type.2.4a: Expected element >>>>>> >>>>>> 'resourceadapter@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> >>>>>> instead of >>>>>> 'dependency@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2' >>>>>> here in element >>>>>> connector@http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 >>>>>> >>>>>> >>>>>> Descriptor: >>>>>> >>>>>> >>>>> xmlns:con="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> db2/db2jcc/8.1.7/jar >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> db2/db2jcc_license_cu/8.1.7/jar >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> db2/db2jcc_license_cisuz/8.1.7/jar >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> javax.sql.DataSource >>>>>> >>>>>> >>>>>> >>>>>> DB2_TEST1 >>>>>> >>>>>> >>>>> name="Password">db2admin >>>>>> >>>>>> >>>>> name="CommitBeforeAutocommit">false >>>>>> >>>>>> >>>>> name="Driver">com.ibm.db2.jcc.DB2Driver >>>>>> >>>>>> >>>>> name="ExceptionSorterClass">org.tranql.connector.AllExceptionsAreFatalSorter >>>>>> >>>>>> >>>>> name="UserName">db2admin >>>>>> >>>>>> >>>>> name="ConnectionURL">jdbc:db2://localhost:50000/TEST1 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Problem-creating-a-DB2-datasource-tp16344329s134p16366049.html >>>>>> Sent from the Apache Geronimo - Users mailing list archive at >>>>>> Nabble.com. >>>>>> >>>> >>> >> > >