Re: Possible problem with grid module
Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 4:26 PM, Sean Kelly wrote: Colleagues: 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. Warm spal wishes, Er, I mean warm swimming wishes, Oops, I mean take care of your pool, GAH! Just thanks OK!?! On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: Hi Guys, 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 ?xml declaration at the top of 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. Here are the steps to reproduce a working Web-Grid with XMLPS: 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= 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. Cheers, Chris [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 On 10/15/10 2:13 PM, David Kale davek...@cs.stanford.edu wrote: 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. Dave On Fri, Oct 15, 2010 at 1:44 PM, David Kale davek...@cs.stanford.eduwrote: Paul, 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. 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. 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? Dave On Fri, Oct 15, 2010 at 1:26 PM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010,
Re: Possible problem with grid module
Hey Dave, 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. Thanks, Paul On Oct 18, 2010, at 10:09 AM, David Kale wrote: Paul, 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. 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. 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. Also, for XMLPS, there is no need to do compile assembly:assembly. Dave On Mon, Oct 18, 2010 at 7:33 AM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 4:26 PM, Sean Kelly wrote: Colleagues: 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. Warm spal wishes, Er, I mean warm swimming wishes, Oops, I mean take care of your pool, GAH! Just thanks OK!?! On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: Hi Guys, 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 ?xml declaration at the top of 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. Here are the steps to reproduce a working Web-Grid with XMLPS: 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= 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. Cheers, Chris [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 On 10/15/10 2:13 PM, David Kale davek...@cs.stanford.edu wrote: 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. Dave On Fri, Oct 15, 2010 at 1:44 PM, David Kale davek...@cs.stanford.edu wrote: Paul, 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
Re: Possible problem with grid module
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, 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. Thanks, Paul On Oct 18, 2010, at 10:09 AM, David Kale wrote: Paul, 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. 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. 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. Also, for XMLPS, there is no need to do compile assembly:assembly. Dave On Mon, Oct 18, 2010 at 7:33 AM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 4:26 PM, Sean Kelly wrote: Colleagues: 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. Warm spal wishes, Er, I mean warm swimming wishes, Oops, I mean take care of your pool, GAH! Just thanks OK!?! On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: Hi Guys, 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 ?xml declaration at the top of 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. Here are the steps to reproduce a working Web-Grid with XMLPS: 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= 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. Cheers, Chris [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 On 10/15/10 2:13 PM, David Kale davek...@cs.stanford.edu wrote: 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
Re: Possible problem with grid module
Not sure if you ran into this while RC¹ing Dave, but the pom.xml for core didn¹t include the Apache snapshots repo. Now, if you have a settings.xml that points to it, you are fine, but I didn¹t on people.a.o...so build didn¹t work for me b/c of pushpull¹s dep on Apache Tika 0.8-SNAPSHOT. Fixed in r1024115. Cheers, Chris On 10/18/10 5:12 PM, David M Woollard wooll...@jpl.nasa.gov wrote: Makes sense to me... onward with the release. -Dave - David M. Woollard, Software Engineer Data Management Systems and Technologies Group (388J) NASA Jet Propulsion Laboratory, Pasadena, CA, 91109, USA Office: 171-243D Phone: (818) 354-4291 Anybody who wants to make a revolution shouldn't grab a gun. Just go and start working to change the world by using science and technology.-Stanford Ovshinsky On Oct 18, 2010, at 4:47 PM, Mattmann, Chris A (388J) wrote: Hi Dave, I¹d say: RC away. It would be great for Dave (K.) to report where in the list of 13 steps below he is getting an error. Talking with him about this over Skype, it seems like he is having some sort of environment issue, though I need to verify that. Either way, Dave (K.) has a work-around and I don¹t think this should prevent the RC. And, even if Dave (K.) *does* think it should prevent the RC, he can VOTE -1, and express that :) Cheers, Chris On 10/18/10 3:22 PM, David M Woollard wooll...@jpl.nasa.gov wrote: 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, 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. Thanks, Paul On Oct 18, 2010, at 10:09 AM, David Kale wrote: Paul, 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. 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. 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. Also, for XMLPS, there is no need to do compile assembly:assembly. Dave On Mon, Oct 18, 2010 at 7:33 AM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 4:26 PM, Sean Kelly wrote: Colleagues: 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. Warm spal wishes, Er, I mean warm swimming wishes, Oops, I mean take care of your pool, GAH! Just thanks OK!?! On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: Hi Guys, 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 ?xml declaration at the top of 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. Here are the steps to reproduce a working Web-Grid with XMLPS: 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
Re: Possible problem with grid module
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. Dave On Fri, Oct 15, 2010 at 1:44 PM, David Kale davek...@cs.stanford.eduwrote: Paul, 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. 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. 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? Dave On Fri, Oct 15, 2010 at 1:26 PM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 1:07 PM, David Kale wrote: Hey fellow OODT developers, 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: java.sql.SQLException: No suitable driver found for jdbc:sqlserver://[REMOVED] To head off the inevitable questions: - 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 It seems inexplicable, but something about substituting the new grid module for the old one is messing up whether the jdbc driver gets loaded...? 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. gratefully, Dave If you want the full stack trace (from catalina.out), here it is: 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 org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.oodt.xmlps.product.DBMSExecutor.executeLocalQuery(DBMSExecutor.java:73) at org.apache.oodt.xmlps.product.XMLPSProductHandler.queryAndPackageResults(XMLPSProductHandler.java:234) at org.apache.oodt.xmlps.product.XMLPSProductHandler.query(XMLPSProductHandler.java:131) at edu.usc.chla.vpicu.bigdata.extraction.handlers.PICUDBQueryHandler.query(PICUDBQueryHandler.java:32) at org.apache.oodt.grid.ProductQueryServlet.handleQuery(ProductQueryServlet.java: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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at
Re: Possible problem with grid module
Colleagues: 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. Warm spal wishes, Er, I mean warm swimming wishes, Oops, I mean take care of your pool, GAH! Just thanks OK!?! On 2010.Oct.15, at 6.16p, Mattmann, Chris A (388J) wrote: Hi Guys, 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 ?xml declaration at the top of 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. Here are the steps to reproduce a working Web-Grid with XMLPS: 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= 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. Cheers, Chris [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 On 10/15/10 2:13 PM, David Kale davek...@cs.stanford.edu wrote: 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. Dave On Fri, Oct 15, 2010 at 1:44 PM, David Kale davek...@cs.stanford.eduwrote: Paul, 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. 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. 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? Dave On Fri, Oct 15, 2010 at 1:26 PM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hey Dave, 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. Thanks, Paul On Oct 15, 2010, at 1:07 PM, David Kale wrote: Hey fellow OODT developers, 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
