Hi, What happens if you run with JDK 5?
Robert On 5/13/08 5:54 AM, "Emmanuel Cecchet" <[EMAIL PROTECTED]> wrote: Hi, > I still have a few questions regarding your reply. I upgraded the MySQL > Connector/J driver to version 5.1.6 and I got the same error. > They probably have a new hierarchy of exception to match JDBC 4. I did not have time to look into that yet, so our generic wrapper might not be able to convert theses MySQL specific exceptions into generic SQLException. >> You will have to force the MySQL Connector/J jar in the controller classpath >> (you can use the XTRA_CLASSPATH environment variable for that) so that >> exceptions can be properly deserialized. >> > > Should I add XTRA_CLASSPATH=$SEQUOIA_HOME\drivers\mysql-connector-5.1.6.jar > to my environment variables list ? > Yes, on both controllers. Right now those jars are only loaded in specific classloaders to access the database but they are not visible to the rest of the controller classes or the group communication libraries, hence the NoClassFoundException when sending back the error. > Previouly I was using mysql-connector-5.1.5 and now i tried > mysql-connector-5.1.6. But I have the same kind of errors. Should I go back > to mysql-connector-5.0 or further older versions. Is it advisable ? > You can keep that driver version, just put the driver in the classpath of the controller. Thanks for your feedback, Emmanuel -- Emmanuel Cecchet FTO @ Frog Thinker Open Source Development & Consulting -- Web: http://www.frogthinker.org email: [EMAIL PROTECTED] Skype: emmanuel_cecchet _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia -- Robert Hodges, CTO, Continuent, Inc. Email: [EMAIL PROTECTED] Mobile: +1-510-501-3728 Skype: hodgesrm
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
