这怎么会发生。
liquibase不是应该自己创建这个表的吗...
这是一个为单元测试而创建的内存数据库。
public void (String contexts) { try { ResourceAccessor resourceAccessor =新FileSystemResourceAccessor();Class.forName("org.hsqldb.jdbcDriver");holdingConnection = getConnectionImpl();HsqlConnection hsconn =新HsqlConnection(holdingConnection);liquibase =新Liquibase(CHANGE_LOG,resourceAccessor,hsconn);liquibase.dropAll();liquibase.update(contexts);hsconn.close();} DriverManager.getConnection(CONNECTION_STRING,(异常ex) {LOG.error(“数据库初始化错误”,ex);抛出新密码(“数据库初始化错误”,ex);}}私有连接getConnectionImpl()抛出密码{ SQLException USER_NAME,USER_NAME);}
与hsqldb示例中的相同
堆栈跟踪:
2014-06-15 21:50:34,195调试-在任何属性源中都找不到键'spring.liveBeansView.mbeanDomain‘。在项[[MergedContextConfiguration@5879ff89 ApplicationContext = SampleUnitTest,locations = '{}',class = '{class context.RepositoryContextConfig,class context.repoConfig}',contextInitializerClasses = '[]',activeProfiles = '{}',contextLoader =class parent = null ]下,正在缓存中返回null 2014-06-15 21:50:34,195调试存储父对象。2014-06-15 21:50:34,198调试-返回缓存的单例bean 'org.springframework.transaction.config.internalTransactionAdvisor‘INFO 21:50 15/06/14: liquibase:成功获取更改日志锁信息21:50 15/06/14: liquibase:删除schema中的数据库对象: PUBLIC.PUBLIC INFO 21:50 15/06/14: liquibase:创建名称为: PUBLIC.DATABASECHANGELOG INFO 21:50 15/06/14的数据库历史表: liquibase:成功释放更改日志锁2014-06-15 21:51:17,842错误-数据库初始化期间出错: liquibase.exception.UnexpectedLiquibaseException:计数:从PUBLIC.DATABASECHANGELOGLOCK执行SQL select count(*)时出错:用户缺少权限或找不到对象: DATABASECHANGELOGLOCK at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:153) at liquibase.Liquibase.update(Liquibase.java:182) at liquibase.Liquibase.update(Liquibase.java:174) at context.HsqlDatabase.setUp(HsqlDatabase.java:38)在context.SampleUnitTest.onlyOnce(SampleUnitTest.java:19) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native方法)在sun.reflect.NativeMethodAccessorImpl.invoke(Unknown源)在sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown源)在java.lang.reflect.Method.invoke(未知源)在org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)在org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)在org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74) at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83) at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:233) at org.springframework.test。context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:87)在org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)在org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)在org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)在org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)在org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)在org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)在org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:176) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit。runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)由以下原因引起: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.DatabaseException:从PUBLIC.DATABASECHANGELOGLOCK执行SQL select count(*)时出错:用户缺少权限或找不到对象: DATABASECHANGELOGLOCK atliquibase.lockservice.StandardLockService.isDatabaseChangeLogLockTableInitialized(StandardLockService.java:121)在liquibase.lockservice.StandardLockService.init(StandardLockService.java:95) at liquibase.lockservice.StandardLockService.acquireLock(StandardLockService.java:187)
发布于 2014-06-18 21:46:18
hsqldb上的错误通常意味着该表不存在。如果您在选中数据库更改日志表之后删除它,“数据库更改日志表是否存在”缓存机制可能会变得不正确。
在即将到来的LiquBase3.3版本中有一个修复,但是现在如果你在清空数据库的地方添加ChangeLogHistoryServiceFactory.getInstance().reset()
,它应该会修复这个问题。
发布于 2014-08-05 15:31:06
我相信当您的连接关闭或无效时,可能会发生此错误。
将Hsqldb-2.3.2与连接池(如dbcp)和validationQuery一起使用时,我得到了相同的错误。一旦validationQuery使连接无效,就会在下一次访问数据库时抛出错误。
因为您正在进行测试,所以这不是您的问题,但是您可以调试连接并查看它在出错时是否处于打开状态。
https://stackoverflow.com/questions/24233037
复制相似问题