So this post is another along the more technical support side. I wanted to create a log of GOTCHAs i've encountered using Sequoia's High Availability database library for my personal reference and to help others with the same problem. sequoia.continuent.org
GOTCHA's
Symptom: My Java Client connects to the virtual database, executes a query, but then sequoia throws a ProtocolException without any information about what went wrong.
Debug: To debug append the 'debugLevel=debug' to your connection URL. You should see information about the connection being made and the authentication working. You should also have the console output of your controllers visable while debugging.
Solution: If you notice WARN messages saying your connection has been closed, it is often due to an incompatible Sequoia driver jar. Assuming you put this driver into your tomcat/lib folder (or where ever) just replace this with the sequoia-driver.jar that matches the installation of sequoia you are using. These drivers appear to not be compatible with any other version than the one they are packaged with!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment