Conflicting PostgreSQL drivers

While deploying the AMDSService (soon to be renamed to GIPSEService) to the training node, we noticed this error:
"SET AUTOCOMMIT TO OFF is no longer supported" being thrown by the AMDSService operations.

This was caused because the training node uses PostgreSQL 8.1 yet the globus_database_common package deploys the JDBC driver for PostgreSQL 7.3 (pg73jdbc2.jar). This causes a problem with the way that ibatis handles postgres connections (specifically ibatis turns autocommit off to maximize performance).

The AMDSService includes the postgreSQL 8 driver (postgresql-8.3-604.jdbc3.jar). To get around this error, we removed the 7.3 driver from the training node's Globus and the training node's Tomcat. Globus is happy using the updated driver, AMDSService is happy using the updated driver and RODSA-DAI is still happy using the updated driver.

This is not a problem for WS-Core Globus installs (like our Windows nodes) since WS-Core doesn't include the 7.3 driver.

Something to keep in mind for any Linux PHGrid nodes that use AMDSService is that they will need to remove the 7.3 postgres driver after installing Globus and the AMDSService. (This is accomplished by renaming $GLOBUS_LOCATION\lib\pg73jdbc2.jar to pg73jdbc2.jar.old; then redeploying Globus to tomcat).

MySQL to PostgreSQL

Today I spent a majority of my time setting up a PostgreSQL resource for the RODS sample database Dr. Espino sent me last week.

PostgreSQL doesn't support the SQL convention for inserting multiple rows at a time. But, I found a way around it by writing an insert function and re-invoking it (which is apparently faster anyways). Thank you Internet.

Tomorrow, I set up the test pulls, and if that goes quickly, I set up the converter and start producing time and spatial series.

Variable JSP

Friday was interesting, the internet was upgraded in the lab and unfortunately that meant all the IP addresses needed to be changed.

Ubuntu does not gracefully handle an IP change... at least not one that is rigged to run VDT installed Globus. The main issue seems to be with MySQL and PostgreSQL, which are configured strangely on ubuntu... and are causing all sorts of connection havoc.

But, I moved a bunch of the code I was working on to a Suse server, got the JSP running again, and now have the ability to pass in different queries. My next set of plans is to get the OpenMRS dataset onto the Suse server and then allow for different pulls from different databases... after that I want to implement a resource discovery subroutine that will work to populate the available resources of a given OGSA-DAI instance.

PHGrid on Ubuntu

Yesterday was spent trying to get the postgresql instance on the second computer running through ogsa-dai, and it failed. Luckily, we found that the original install of OGSA-DAI was working and a few servers just hadn't been restarted since the last time it was shut down.

Thus, today, I went ahead and tried some of the other example clients on that server and actually got the secure communications set up with the help of Dan and Alastair.

The other big news is that we got the Ubuntu box installed yesterday, so today we made headway in getting a VDT install of Globus on Ubuntu, it is almost up and running, now we are just dealing with all of the certificate and authentication stuff, then it will be setting up tomcat, deploying OGSA-DAI, and probably setting up a little mysql database.

As for the "second computer" I am going to try and get MySQL running on it too.. then we can start trying to code OGSA-DAI proofs of concepts that pull from a PostgreSQL database and two MYSQL databases on three different computers.

Cheers,