I’m experiencing this, but with v2.0.1 and Derby v10.8.1.2:
I’m running Liquibase from my java app and have it set up similar to the suggestion here:
However, I’m not calling connection.rollback() before connection.close(). Calling connection.rollback() gets rid of the error, but I don’t understand why it’s needed or what effect it’s going to have (is it going to rollback an important transaction?).
I get the error without any changesets running. I don’t get the error when I switch to the maven plugin instead of my own code. The SpringLiquibase class in the integration package does connection.getAutoCommit() and a rollback if it returns false. I tried setting connection.setAutoCommit(true) in my code, but it doesn’t make any difference.
I found this old mailing list thread that might hint at the underlying cause:
Any suggestions? I can post my code or even do a quick sample project if it helps. Just ask.