Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,

    Make sure you are using InnoDB storage engine and READ-COMMITTED transaction isolation level and increase the database server innodb_lock_wait_timeout variable to about 500.

Solutions on the web

via Mirth Project by Brent Moen, 1 year ago
Failed to execute script: mysql-9-3.0.0-1.sql
via Mirth Project by Brent Moen, 2 years ago
Failed to execute script: mysql-9-3.0.0-1.sql
com.mirth.connect.model.util.MigrationException: Failed to execute script: mysql-9-3.0.0-1.sql at com.mirth.connect.server.migration.Migrator.executeScript( at com.mirth.connect.server.migration.Migrate3_0_0.migrate( at com.mirth.connect.server.migration.ServerMigrator.migrate( at com.mirth.connect.server.controllers.DefaultMigrationController.migrate( at com.mirth.connect.server.Mirth.startup( at at com.mirth.connect.server.Mirth.main( by: java.sql.SQLException: Can't execute the given command because you have active locked tables or an active transaction at com.mysql.jdbc.SQLError.createSQLException( at com.mysql.jdbc.MysqlIO.checkErrorPacket( at com.mysql.jdbc.MysqlIO.checkErrorPacket( at com.mysql.jdbc.MysqlIO.sendCommand( at com.mysql.jdbc.MysqlIO.sqlQueryDirect( at com.mysql.jdbc.ConnectionImpl.execSQL( at com.mysql.jdbc.ConnectionImpl.execSQL( at com.mysql.jdbc.StatementImpl.execute( at com.mysql.jdbc.StatementImpl.execute( at com.mirth.connect.server.migration.Migrator.executeScript( ... 6 more