Could not update Activiti database schema: unknown version from database: ‘5.x.x.x‘
2017-11-22 22:46
579 查看
Could not update Activiti database schema: unknown version from database: ‘5.x.x.x‘
1. 明明是web项目,却部署不到tomcat上?项目右键--property--Project Facets,选中Dynamic Web Module(选择原项目web版本,一般3.0都没错),选中Java(选择对应的JDK版本),保存,刷新项目即可。
2. 启动tomcat后,发现无法访问到主页面了?
我遇到的情况是web.xml没有加载,因为项目指定了另一个web.xml文件,但是项目部署时却依然加载原文件,此时就需要我们修改web.xml的指定路径了。两种方法如下:
a. 打开该项目的工作区间,找到.setting 文件夹下的 org.eclipse.wst.common.component文件,找到
[html] view
plain copy
<wb-module deploy-name="AMS">
<wb-resource deploy-path="/" source-path="/WebContent "/>
将WebContent改为你的webRoot目录名即可(maven项目,我们是放到这里src/main/webapp)。如果没有这一行,就自行加上去。
同上,找到.jsdtscope 文件中的
<classpathentry kind="src" path=" WebContent "/>改成与上面的 source-path一致即可
b. 后来发现,改这两个配置文件时灵时不灵,可以有另一种方法:指定的src/main/webapp下的web.xml没有加载,而默认加载了Webcontent下的web.xml,是因为指定的编译路径有问题!
项目右键>Properties>Deployment Assembly,将默认的Webcontent移除,src/main/webapp的编译路径改为根目录:'/'
3. 运行程序时,提示Errors running builder "Integrated External Tool Builder" on project,
The builder launch configuration could not be found ?
项目右键-Properties-Builders,将带有红感叹号的移除。
4. maven项目中jar包缺失?从网上下也下不到?
可能有两种情况:
a. 指定的远程仓库已经关闭,停止服务(比如开源中国,maven仓库就关闭了)。判断的方法是直接访问仓库的网址,看能否成功。如果确实关闭了,可以指定其他仓库
b. 缺失的jar包为一些开源的工具开发包,在maven仓库可能没有资源。这种情况,可以先到几个主流的maven仓库搜索资源,如果确实没有,就只能自己手动安装jar包到本地仓库了。手动安装网上资源很多就不赘述了。
5. 启动tomcat时, validator注入失败Causedby:java.lang.NoClassDefFoundError:javax/validation/ParameterNameProvider?
这时就需要将javax.validation更新到较高版本,因为hibernate-validator-5.x.x已经不兼容validation-api-1.0.x,hibernate- validator-5.x.xhibernate-validator-5.x.x把旧的校验框架JSR-303,改变为JSR-349了。在pom.xml中添加
[html] view
plain copy
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.1.0.Final</version>
</dependency>
6. 启动tomcat报错:Could not update Activiti database schema: unknown version from database: ‘5.x.x.x‘?
将数据库中已存在的activiti的25张表删除即可。(此处用到了这个解决报错问题,将项目中的activiti工作流相关的表都删掉了,问题解决)
感恩原作者:http://blog.csdn.net/jiangzhongwei_/article/details/53036176
补充:
今天再次遇到了 " Could not update Activiti database schema: unknown version from database: '5.21.1'" 这个问题,问题定位到了,原因是: activiti 相关的jar版本和表 act_ge_property 中 schema.version 所存储的版本不一致导致报错的。
解决办法是:act_ge_property
表中的 schema.version
字段版本修改为和 activiti jar包版本一致即可。
正确的配置如下:
错误配置参考:
2018年1月6日 16:05:02
相关文章推荐
- Could not update Activiti database schema: unknown version from database: '5.20.0.1'
- Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
- System.TypeLoadException: Could not load type 'System.DateTimeOffset' from assembly 'mscorlib, Version=2.0.0.0
- 解决Connections could not be acquired from the underlying database!的问题
- 自动化测试 appium Could not detect Mac OS X Version from sw_vers output: '10.12.3 ' 异常处理
- 解决:Connections could not be acquired from the underlying database!
- .NET Web 执行错误Could not load type '...' from assembly '..., Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because the me
- 解决:Connections could not be acquired from the underlying database!
- Connections could not be acquired from the underlying database问题解决
- Could not update the distribution database subscription table. The subscription status could not be changed.
- 用pip安装pymongo模块报错:Could not find a version that satisfies the requirement pymongo(from version:)
- 用pip安装pymongo模块报错:Could not find a version that satisfies the requirement pymongo(from version:)
- Vitamio 导入依赖库出错 :Error:(9, 0) Could not get unknown property 'ANDROID_BUILD_SDK_VERSION' for project
- Could not get unknown property 'ANDROID_BUILD_SDK_VERSION'
- java.sql.SQLException: Connections could not be acquired from the underlying database!
- Connections could not be acquired from the underlying database
- 错误中学习--Connections could not be acqu 4000 ired from the underlying database
- Could not get unknown property 'ANDROID_BUILD_SDK_VERSION'
- Connections could not be acquired from the underlying database
- 连接数据库出现:Connections could not be acquired from the underlying database