So after long hours of testing and even using temporarily for production I have been running into a huge issue with Sequoia. The first problem is not that far out there as I would expect a database layer that encompasses several backends to not provide database specific support, but the issue that the failure causes is catastrophic for a production environment.
Inserts with Sequoia are very tricky, commands that would work directly on a postgresql connection often generate errors when run through the sequoia layer, specifically with auto-incrementing sequences. This also happens if I you accidentally try to create a table that already exists and probably under other circumstances as well. Upon execution of a command like such a RAIDb level:1 failure occurs and produces a stack trace like: ERROR continuent.hedera.adapters PullPushAdapter: Error while reading from channel Org.continuent.appia.core.message.MessageException: Trying to read an unknown object from message . This failure is fine and a work around could be investigated. The big issues is that when anything like this happens the connections are not closed and continue to fillup the maximum connection queue. After a while in production with maybe just a few bad queries; the database locks up because no more connections can be processed. So not only is some Data not getting inserted into the database but users eventually lose the ability to read as well! Is there any way to cope with this issue, or disable the connections from staying open? Is there a way to do a complete pass through of commands to the postgresql driver so they execute properly (as we only use postgres)? Thanks in advance, Martin Dale Lyness MagnetStreet <http://www.magnetstreet.com/> [EMAIL PROTECTED] Office: (763) 450-7503 Cell: (715) 630-0296
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
