Jin,
I tested again using one tomcat server and two MySQL backends and
looks working fine but I get a lot of warning messages, though. What
are those warnings about and how I can remove those warnings?
15:51:10,066 WARN backend.DatabaseBackend.tareka09 Unable to find
table $tmp_bs1301 in database schema, when getting next entry to
execute : DROP TABLE $tmp_bs1301/
15:51:10,067 WARN backend.DatabaseBackend.tareka08 Unable to find
table $tmp_bs1301 in database schema, when getting next entry to
execute : DROP TABLE $tmp_bs1301/
It is strange that you always get the warning multiple times on the same
table. There are 2 possible causes:
- the temporary table is not reported by MySQL when we fetch the schema
because its scope is only visible in the connection where it was
created. In that case, you should use persistent connections (add
?persistentConnections=true at the end of your Sequoia JDBC URL)
- there is a bug in the application that does not allocate unique
temporary table names (that are visible for all connections) and tries
to drop multiple times the same table (the database usually does not
complain but only the first drop will succeed)
Keep us posted with your findings,
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
