On Fri, Jul 25, 2008 at 1:55 PM, Alex Viggio <[EMAIL PROTECTED]> wrote: > I tried installing the latest MySQL JAR (5.1.6), but am seeing an > older 3.1.13 JAR released circa 05-26-06. Could this be a problem or > does that Nuxeo module require 3.1.13? > > $ find . -name "mysql*.jar" > ./server/default/tmp/deploy/tmp6546nuxeo-platform-directory-sql-5.1.5.jar-contents/lib/mysql-connector-java-3.1.13.jar > ./server/default/lib/mysql-connector-java-5.1.6-bin.jar > > $ grep -Ri mysql-connector-java-3.1.13 * > Binary file > server/default/deploy/nuxeo.ear/platform/nuxeo-platform-directory-sql-5.1.5.jar > matches
I may have made some progress here, but appreciate your feedback. I'll also know more in the next 24 hours if our MySQL remote connection issues improve. The impetus here was trying to get <valid-connection-checker-class-name> datasource config working. When I added this config to my datasources, I started seeing "java.sql.SQLException: Ping failed: java.lang.IllegalArgumentException: object is not an instance of declaring class" errors when I would restart Nuxeo. So I decided to try ripping out the old MySQL Connector/J 3.1.13 that I'd uncovered earlier. Essentially, I unpacked the following jar and renamed the obsolete MySQL JAR, e.g. ../nuxeo-platform-directory-sql-5.1.5.jar/lib/mysql-connector-java-3.1.13.ja_ server/default/deploy/nuxeo.ear/platform/nuxeo-platform-directory-sql-5.1.5.jar When I restart Nuxeo, I no longer am bombarded by those IllegalArgumentExceptions. Hopefully nuxeo-platform-directory-sql is forwards compatible with the newest GA Connector/J. Will report back if it seems to help (or not), but any input is appreciated if someone has tried this before. More specifically, could someone at Nuxeo clarify why you are bundling mysql-connector-java-3.1.13.jar in that Nuxeo platform JAR or maybe this was an oversight? Thanks, - Alex _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
