Randall,
Sequoia is telling me that it cannot find classes which are in the
MySQL driver jar when an error occurs. For example, if I issue the
statement "seDect * from table", the controller will print out that it
cannot find the MySQLSyntaxException <-- that's just a guess, the
actual name is something like that.
I've looked into the MySQL driver jar and the class is there and
obviously since I'm talking to the MySQL database, Sequoia has found
the jar so.... ? I'm lost as to why it cannot find the class.
This is a classloader problem. A proper driver is supposed to return an
SQLException and not an implementation specific class. The Sequoia
controller has a smart classloader that automatically scans the driver
directory to find driver related class. Unfortunately, the group
communication library does not use this classloader and cannot access
driver specific classes unless they are found in the classpath of the JVM.
A solution to your problem is to unjar your MySQL driver jar file in the
drivers/ directory or add it explicitely to the controller classpath
(for example in the XTRA_CLASSPATH environment variable) and that should
solve the issue.
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
