This is related to the network. You can also try to run the Server as an HTTP server (Use WebServer instead of Server) and see if that works.
Execute SHUTDOWN as an SQL command.
If you create databases that do not need to stay open, SHUTDOWN the databases. If the databases need to stay open, Increase the JVM memory allocation or reduce the CACHE ROWS and CACHE SIZE settings.
It seems what is happening is the column gets added OK. But you probably have a procedure that does something like this which assumes a certain number of columns INSERT INTO MY TABLES VALUES 1, 2, 3 When you add the column, the INSERT statement is recompiled and it fails. So you must first do ALTER SPECIFIC ROUTINE and change the routine so it doesn't reference the table. Then do the ALTER TABLE ADD COLUMN Then do ALTER SPECIFIC ROUTINE again with an updated INSERT (or other) statement. See the Guide...
It is simply wrong. Open the database with the writer connection and close this connection last. This does the lock aquisition and no further failure will occur.
readonly=true is wrong, because the database is not readonly.
RowStoreAVLMemory is used for INFORMATION_SCHEMA tables. RowStoreAVLHybrid is used for result sets when result_max_memory_rows is exceeded RowStoreAVLDisk is used for CACHED table. All the above extend RowStoreAVL Your usage may cause many such objects being allocated.
Use this: offset INTERVAL SECOND(6) NOT NULL