Return-Path: Delivered-To: apmail-incubator-oodt-dev-archive@minotaur.apache.org Received: (qmail 54628 invoked from network); 18 Oct 2010 22:23:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Oct 2010 22:23:19 -0000 Received: (qmail 44222 invoked by uid 500); 18 Oct 2010 22:23:19 -0000 Delivered-To: apmail-incubator-oodt-dev-archive@incubator.apache.org Received: (qmail 44189 invoked by uid 500); 18 Oct 2010 22:23:18 -0000 Mailing-List: contact oodt-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oodt-dev@incubator.apache.org Delivered-To: mailing list oodt-dev@incubator.apache.org Received: (qmail 44181 invoked by uid 99); 18 Oct 2010 22:23:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 22:23:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [128.125.137.216] (HELO msg-ironport2.usc.edu) (128.125.137.216) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 22:23:12 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApEBAGZlvExGt1PC/2dsb2JhbAAH404ChUcEhFQ4HQ X-IronPort-AV: E=Sophos;i="4.57,346,1283756400"; d="scan'208";a="436033463" Received: from wsip-70-183-83-194.sd.sd.cox.net (HELO [172.17.37.236]) ([70.183.83.194]) by msg-ironport2.usc.edu with ESMTP/TLS/AES128-SHA; 18 Oct 2010 15:22:51 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: Possible problem with "grid" module From: David M Woollard In-Reply-To: <14D6ECB6-8C50-4155-805A-E5F344FA8D63@jpl.nasa.gov> Date: Mon, 18 Oct 2010 15:22:49 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4441D50B-309B-4CA3-BBD7-9B09E1A06475@jpl.nasa.gov> References: <767C42F7-94A8-4C6D-975E-606E54EEC0EB@apache.org> <3BC28454-A92C-4438-BB8B-42E97B688384@jpl.nasa.gov> <14D6ECB6-8C50-4155-805A-E5F344FA8D63@jpl.nasa.gov> To: "oodt-dev@incubator.apache.org" X-Mailer: Apple Mail (2.1077) X-Virus-Checked: Checked by ClamAV on apache.org Hey Guys, I'm starting work on a RC for 0.1-incubating. I have just been doing = some basic setup stuff (pgp keys and the whatnot), so I have not yet = made a RC tag. Paul, do you want a little time to work this issue? = Sounds like it is not a blocker for the release, but I can hold off for = a couple hours if you have the cycles to do it now. -Dave On Oct 18, 2010, at 3:15 PM, Ramirez, Paul M (388J) wrote: > Hey Dave, >=20 > Thanks for the follow up sounds like we may have a bug in the = conversion over to Apache for this component in the way it references = the path to the driver. Can you open an issue on this component in = essentially using your email and state the environment you are running = in. Feel free to assign the issue to me if you have the ability when = creating the issue. >=20 > Thanks, > Paul >=20 > On Oct 18, 2010, at 10:09 AM, David Kale wrote: >=20 >> Paul, >>=20 >> Thank you for following up and reminding me to send you guys an = update. No, >> Chris' changes and his set of instructions did not help me out. >>=20 >> Basically what we come down to is the following: I'm using the jtds = driver >> to connect to a SQL Server. *When I use the web-grid configuration = page to >> specify the path to the driver jar file in the code bases, I get the = "no >> suitable driver found" error. If I manually copy the driver jar file = into >> $TOMCAT/webapps/grid/WEB-INF/lib, it works just fine. *I would = further add >> that I'm also using the configuration page to point to XMLPS, and = that works >> just fine. It's quite bizarre. >>=20 >> The good news is that I have something working (by manually copying = the jar >> file), but in the long run, we should try to figure this out, I = suppose. >>=20 >> Also, for XMLPS, there is no need to do compile assembly:assembly. >>=20 >> Dave >>=20 >>=20 >>=20 >> On Mon, Oct 18, 2010 at 7:33 AM, Ramirez, Paul M (388J) < >> paul.m.ramirez@jpl.nasa.gov> wrote: >>=20 >>> Hey Dave, >>>=20 >>> Was taken out by a cold this weekend did Chris' changes resolve your = issue? >>> If not let me know and I'll try to test out an install of webgrid = from >>> Apache OODT as Chris outlined below. >>>=20 >>> Thanks, >>> Paul >>>=20 >>> On Oct 15, 2010, at 4:26 PM, Sean Kelly wrote: >>>=20 >>>> Colleagues: >>>>=20 >>>> Thanks for fixing the old jpl.eda references in web-grid. As it was >>> neglected in the original import of OODT code from JPL into the = Apache >>> Incubator, it did not get the rigorous examination that we afforded = the >>> other components. >>>>=20 >>>> Warm spal wishes, >>>> Er, I mean warm swimming wishes, >>>> Oops, I mean take care of your pool, >>>> GAH! >>>> Just thanks OK!?! >>>>=20 >>>>=20 >>>>=20 >>>> On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: >>>>=20 >>>>> Hi Guys, >>>>>=20 >>>>> OK I was able to checkout a fresh copy of Apache OODT from = Incubator >>> SVN, build Web-Grid, XMLPS and then connect to a local Postgres DB = with some >>> dummy data in it on my local machine and do a query and it worked. I = did >>> find one (documentation) bug wherein which the example XML mapping = file >>> checked in for XMLPS doesn't put the >> file and thus won't parse. I've filed an issue OODT-46 [1] and will = commit a >>> fix for that shortly. I also noticed that the Web-Grid pages mention = classes >>> that implement the jpl.eda.product... Interfaces rather than >>> org.apache.oodt.product... so I've filed OODT-47 [2] to fix that. = Finally I >>> fixed an issue with WildcardLiterals in OODT-48 [3] and have fixed = that. >>>>>=20 >>>>> Here are the steps to reproduce a working Web-Grid with XMLPS: >>>>>=20 >>>>>=20 >>>>> 1. svn co latest OODT from trunk >>>>> 2. mvn install from OODT/trunk top level >>>>> 3. cd grid >>>>> 4. mvn package war:war (builds = target/web-grid-0.1-incubating.war) >>>>> 5. cd ../xmlps >>>>> 6. mvn package assembly:assembly (builds >>> target/oodt-xmlps-0.1-incubating-with-dependencies.jar) >>>>> 7. create test area, e.g., /usr/local/xmlpstest and copy >>> oodt-xmlps-0.1-incubating-with-dependencies.jar to it >>>>> 8. copy example conf files out of xmlps/src/main/conf >>> (example.db.properties and example-ps.xml) into test area >>>>> 9. modify examples for your database (I used a local postgres = instance >>> and I created a simple mapping file with 2 fields, one dynamic and = one >>> constant that queried 1 database) >>>>> 10. copy WAR file to $TOMCAT_HOME/webapps/grid.war >>>>> 11. visit http://localhost:8080/grid/ >>>>> 12. Configure web-grid after logging in to use XMLPS handler, to >>> reference your JDBC jar file (that you copy into = /usr/local/xmlpstest), and >>> to reference XMLPS jar file in /usr/local/xmlpstest >>>>> 13. try a query at: http://localhost:8080/grid/prod?q=3D >>>>>=20 >>>>>=20 >>>>> Would be great to turn the above into some XDOCS for webgrid and = for >>> xmlps :) I'll do it later if no one else does, probably after the >>> 0.1-incubating release. >>>>>=20 >>>>> Cheers, >>>>> Chris >>>>>=20 >>>>> [1] https://issues.apache.org/jira/browse/OODT-46 >>>>> [2] https://issues.apache.org/jira/browse/OODT-47 >>>>> [3] https://issues.apache.org/jira/browse/OODT-48 >>>>>=20 >>>>>=20 >>>>> On 10/15/10 2:13 PM, "David Kale" = wrote: >>>>>=20 >>>>> Follow up: I have confirmed that the "config.xml" file is being = read >>>>> correctly (i.e., it has the location of the DB props file). Next = gotta >>>>> figure out who reads that and whether it's being read correctly. >>>>>=20 >>>>> Dave >>>>>=20 >>>>> On Fri, Oct 15, 2010 at 1:44 PM, David Kale = >>> wrote: >>>>>=20 >>>>>> Paul, >>>>>>=20 >>>>>> Thanks for the response. I have a standard Tomcat 5.5.28 set up = on my >>>>>> 10.6-running Mac Pro (though I get the same issue on an Ubuntu = system >>> that >>>>>> CMAT set up). I'm using the Tomcat Manager page to deploy the = grid war >>> file >>>>>> (both the old and the new), and I copy over a backed-up war file = after >>>>>> deployment (but before opening the grid Configure page), so it = gets >>> loaded >>>>>> up when I visit the grid Configure page. >>>>>>=20 >>>>>> Anyway, I am strongly inclined against the idea that I've somehow >>> messed up >>>>>> some configuration here or there. I am following exactly the = same >>> procedure >>>>>> for deploying the old grid module and the new grid module, with = the >>>>>> aforementioned divergent results. I think there may be something = in >>> grid >>>>>> itself. >>>>>>=20 >>>>>> I would also add that if you do jar tf on each of the grid war = files >>> (old >>>>>> and new), you see pretty different contents, including some oodt >>> modules >>>>>> (such as grid-profile/grid-product) that are in the old one but = not the >>> new >>>>>> one (and which, it would seem from looking at them, do some stuff = with >>> the >>>>>> DB props file). Perhaps the new grid is missing some = functionality >>> from >>>>>> there? >>>>>>=20 >>>>>> Dave >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Fri, Oct 15, 2010 at 1:26 PM, Ramirez, Paul M (388J) < >>>>>> paul.m.ramirez@jpl.nasa.gov> wrote: >>>>>>=20 >>>>>>> Hey Dave, >>>>>>>=20 >>>>>>> Where are you putting the config file? Have you tried shutting = down >>> Tomcat >>>>>>> and removing the work directory? This directory is simply a = cache >>> Tomcat >>>>>>> creates and will be recreated when restarted. If you provide a = few >>> more >>>>>>> details on how you are deploying the app and possibly the config = file >>> and >>>>>>> server.xml file for Tomcat I might be able to help out. I = haven't >>> deployed >>>>>>> grid module before but the output below seems like a = configuration >>> issue. >>>>>>>=20 >>>>>>> Thanks, >>>>>>> Paul >>>>>>>=20 >>>>>>> On Oct 15, 2010, at 1:07 PM, David Kale wrote: >>>>>>>=20 >>>>>>>> Hey fellow OODT developers, >>>>>>>>=20 >>>>>>>> At CHLA we're trying to deploy the grid module (in conjunction = with >>>>>>> XMLPS) >>>>>>>> to serve data from a SQL Server. We had it working with the = "old" >>> grid >>>>>>>> module (from the jpl.eda namespace), but once we substituted = the new >>>>>>> grid >>>>>>>> module, we started getting the following: >>>>>>>>=20 >>>>>>>> java.sql.SQLException: No suitable driver found for >>>>>>>> jdbc:sqlserver://[REMOVED] >>>>>>>>=20 >>>>>>>> To head off the inevitable questions: >>>>>>>>=20 >>>>>>>> - The jar file with the driver is in the right place, and the = config >>>>>>>> points to it. >>>>>>>> - The config file is, in fact, virtually identical to the = config I >>>>>>> used >>>>>>>> for the "old" grid (only difference is a different query = handler, >>>>>>> which >>>>>>>> isn't relevant) >>>>>>>> - Yes, I am using JDK 1.6 (not 1.5), but JDK 1.6 works fine for = old >>>>>>> grid, >>>>>>>> so I can't imagine why that would be the issue here >>>>>>>>=20 >>>>>>>> It seems inexplicable, but something about substituting the new = grid >>>>>>> module >>>>>>>> for the old one is messing up whether the jdbc driver gets = loaded...? >>>>>>>>=20 >>>>>>>> Chris has some ideas about what might be going on, and I'm = going to >>> keep >>>>>>>> debugging, but we wanted to put the conversation out in the = public, >>>>>>> rather >>>>>>>> than in a Skype window. >>>>>>>>=20 >>>>>>>> gratefully, >>>>>>>> Dave >>>>>>>>=20 >>>>>>>> If you want the full stack trace (from catalina.out), here it = is: >>>>>>>>=20 >>>>>>>> java.sql.SQLException: No suitable driver found for >>>>>>>> jdbc:sqlserver://[REMOVED] >>>>>>>> at java.sql.DriverManager.getConnection(DriverManager.java:602) >>>>>>>> at java.sql.DriverManager.getConnection(DriverManager.java:185) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(Dr= iverManagerConnectionFactory.java:48) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConne= ctionFactory.java:290) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectP= ool.java:771) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.= java:95) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.oodt.xmlps.product.DBMSExecutor.executeLocalQuery(DBMSExecutor.= java:73) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.oodt.xmlps.product.XMLPSProductHandler.queryAndPackageResults(X= MLPSProductHandler.java:234) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.oodt.xmlps.product.XMLPSProductHandler.query(XMLPSProductHandle= r.java:131) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = edu.usc.chla.vpicu.bigdata.extraction.handlers.PICUDBQueryHandler.query(PI= CUDBQueryHandler.java:32) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.oodt.grid.ProductQueryServlet.handleQuery(ProductQueryServlet.j= ava:59) >>>>>>>> at = org.apache.oodt.grid.QueryServlet.doPost(QueryServlet.java:100) >>>>>>>> at = org.apache.oodt.grid.QueryServlet.doGet(QueryServlet.java:75) >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:627) >>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicati= onFilterChain.java:269) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter= Chain.java:188) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.= java:213) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.= java:172) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1= 27) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1= 17) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja= va:108) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174= ) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873)= >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proces= sConnection(Http11BaseProtocol.java:665) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.j= ava:528) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollower= WorkerThread.java:81) >>>>>>>> at >>>>>>>>=20 >>>>>>>=20 >>> = org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j= ava:689) >>>>>>>> at java.lang.Thread.run(Thread.java:637) >>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>> Chris Mattmann, Ph.D. >>>>> Senior Computer Scientist >>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>>> Office: 171-266B, Mailstop: 171-246 >>>>> Email: Chris.Mattmann@jpl.nasa.gov >>>>> WWW: = http://sunset.usc.edu/~mattmann/ >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>> Adjunct Assistant Professor, Computer Science Department >>>>> University of Southern California, Los Angeles, CA 90089 USA >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>=20 >>>>=20 >>>=20 >>>=20 >=20