【springboot整合flowable6.6.0启动报错-已解决】

最新推荐文章于 2024-01-04 19:04:06 发布
最新推荐文章于 2024-01-04 19:04:06 发布
阅读量3.7k 收藏 1
点赞数 1
分类专栏： 异常处理 文章标签： mysql java Springboot flowable
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/cjiankai/article/details/122056545
版权

问题描述

今天想基于SpringBoot2.3.4.Release整合Flowable6.6.0，在启动项目过程中flowable会自动创建数据库表，但是没曾想，报错了~

贴上报错的日志

2021-12-21 10:19:33.149  INFO 1128 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2021-12-21 10:19:33.582  INFO 1128 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
2021-12-21 10:19:34.484  INFO 1128 --- [           main] o.f.a.s.SpringAppEngineConfiguration     : Executing configure() of class org.flowable.engine.spring.configurator.SpringProcessEngineConfigurator (priority:50000)
Opening JDBC Connection
2021-12-21 10:19:34.718 ERROR 1128 --- [           main] o.f.c.e.impl.db.CommonDbSchemaManager    : Could not get property from table ACT_GE_PROPERTY

java.sql.SQLSyntaxErrorException: Table 'flow_bpmn.act_ge_property' doesn't exist
	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120) ~[mysql-connector-java-8.0.21.jar:8.0.21]
	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97) ~[mysql-connector-java-8.0.21.jar:8.0.21]
	at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-java-8.0.21.jar:8.0.21]
	at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:953) ~[mysql-connector-java-8.0.21.jar:8.0.21]
	at com.mysql.cj.jdbc.ClientPreparedStatement.executeQuery(ClientPreparedStatement.java:1003) ~[mysql-connector-java-8.0.21.jar:8.0.21]
	at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeQuery(ProxyPreparedStatement.java:52) ~[HikariCP-3.4.5.jar:na]
	at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeQuery(HikariProxyPreparedStatement.java) ~[HikariCP-3.4.5.jar:na]
	at org.flowable.common.engine.impl.db.AbstractSqlScriptBasedDbSchemaManager.getProperty(AbstractSqlScriptBasedDbSchemaManager.java:191) ~[flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.db.ServiceSqlScriptBasedDbSchemaManager.getSchemaVersion(ServiceSqlScriptBasedDbSchemaManager.java:111) [flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.db.ServiceSqlScriptBasedDbSchemaManager.schemaUpdate(ServiceSqlScriptBasedDbSchemaManager.java:67) [flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.db.ProcessDbSchemaManager.schemaUpdate(ProcessDbSchemaManager.java:215) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.SchemaOperationsProcessEngineBuild.execute(SchemaOperationsProcessEngineBuild.java:54) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.SchemaOperationsProcessEngineBuild.execute(SchemaOperationsProcessEngineBuild.java:28) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.interceptor.CommandInvoker$1.run(CommandInvoker.java:59) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperation(CommandInvoker.java:107) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperations(CommandInvoker.java:81) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:64) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.interceptor.BpmnOverrideContextInterceptor.execute(BpmnOverrideContextInterceptor.java:26) [flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.interceptor.TransactionContextInterceptor.execute(TransactionContextInterceptor.java:53) [flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:83) [flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.common.spring.SpringTransactionInterceptor.lambda$execute$0(SpringTransactionInterceptor.java:57) [flowable-spring-common-6.6.0.jar:6.6.0]
	at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) ~[spring-tx-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:57) [flowable-spring-common-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30) ~[flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56) ~[flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.ProcessEngineImpl.<init>(ProcessEngineImpl.java:82) ~[flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:981) ~[flowable-engine-6.6.0.jar:6.6.0]
	at org.flowable.spring.SpringProcessEngineConfiguration.buildProcessEngine(SpringProcessEngineConfiguration.java:75) ~[flowable-spring-6.6.0.jar:6.6.0]
	at org.flowable.engine.spring.configurator.SpringProcessEngineConfigurator.initProcessEngine(SpringProcessEngineConfigurator.java:60) ~[flowable-spring-configurator-6.6.0.jar:6.6.0]
	at org.flowable.engine.spring.configurator.SpringProcessEngineConfigurator.configure(SpringProcessEngineConfigurator.java:49) ~[flowable-spring-configurator-6.6.0.jar:6.6.0]
	at org.flowable.common.engine.impl.AbstractEngineConfiguration.configuratorsAfterInit(AbstractEngineConfiguration.java:1036) ~[flowable-engine-common-6.6.0.jar:6.6.0]
	at org.flowable.app.engine.AppEngineConfiguration.init(AppEngineConfiguration.java:235) ~[flowable-app-engine-6.6.0.jar:6.6.0]
	at org.flowable.app.engine.AppEngineConfiguration.buildAppEngine(AppEngineConfiguration.java:192) ~[flowable-app-engine-6.6.0.jar:6.6.0]
	at org.flowable.app.spring.SpringAppEngineConfiguration.buildAppEngine(SpringAppEngineConfiguration.java:65) ~[flowable-app-engine-spring-6.6.0.jar:6.6.0]
	at org.flowable.app.spring.AppEngineFactoryBean.getObject(AppEngineFactoryBean.java:59) ~[flowable-app-engine-spring-6.6.0.jar:6.6.0]
	at org.flowable.app.spring.AppEngineFactoryBean.getObject(AppEngineFactoryBean.java:31) ~[flowable-app-engine-spring-6.6.0.jar:6.6.0]
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:169) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:101) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1828) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.getObjectForBeanInstance(AbstractAutowireCapableBeanFactory.java:1265) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.addCandidateEntry(DefaultListableBeanFactory.java:1532) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1489) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1270) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1227) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:884) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:788) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:538) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1336) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1176) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:556) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:897) ~[spring-beans-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:879) ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:551) ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:143) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:758) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:750) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1237) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.3.4.RELEASE.jar:2.3.4.RELEASE]
	at com.jkhub.flow.bpmn.FlowApplication.main(FlowApplication.java:16) ~[classes/:na]

分析原因

在不断查找分析问题，发现flowable启动的时候会遍历当前数据库连接下的所有库表进行查询（因为使用的是root用户登录）如果其他库，有flowable相关表的话，就会被判定为不缺少表。默认情况下，就不会进行表更新操作。但是在实例化对象的时候，又无法查到相关数据，所以会在启动时报错。

解决问题

针对这个问题，我们只需要在数据库连接配置上加&nullCatalogMeansCurrent=true，因为默认是false，如下图所示：
在这里插入图片描述

Of Chen
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
springBoot 整合flowable-modeler设计器
03-06
springboot 整合flowable-modeler 设计器
Spring Boot 整合 Flowable-ui-modeler 6.7.2代码
04-15
网上的都是整合 Flowable-ui-modeler的其他的低版本，当前Flowable版本为6.7.2，所以这个地方做了整合。 正说说明文档地址： https://blog.csdn.net/wangdaoyin2010/article/details/124187676
springboot-flowable-cims基于工作流引擎flowable、spring boot开发的工作流服务平台
06-26
springboot-flowable-cims基于工作流引擎flowable、spring boot开发的工作流服务平台，完美整合官方flowable modeler 进行流程设计、表单设计。提供flowable rest api 接口 供后台业务系统流程调用。提供前后端分离后台管理进行模拟流程测试、流程管理
flowable-engine-flowable-6.6.0.zip
07-06
flowable6.6.0 源码
Flowable 6.6.0 应用指南 - Eclipse设计器.pdf
03-04
2021年3月最新修订版。Flowable附带了一个Eclipse插件，即Flowable Eclipse设计器（Flowable Eclipse Designer），可用于图形化地建模、测试和部署BPMN 2.0流程
nested exception is org.flowable.common.engine.api.FlowableException: Error initialising dmn data mo
qq_43102730的博客
06-15 3507
FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Error initialising dmn data model在启动Flowable和Spring Boot继承的项目时报如下错误： 后来经过排查发现是mysql的问题解决方法：找到数据库所表名以 databasechangeloglock 为后缀的表，并改成如下图格式问
Flowable从零单排（五）集成Springboot
江黎
03-02 4396
Spring Boot提倡约定大于配置。要开始工作，只需在项目中添加flowable-spring-boot-starter或flowable-spring-boot-starter-rest依赖。如果不需要引入所有的引擎，可以查看其它的Flowable starter。 如使用Maven： <dependency> <groupId>org.flowable</groupId> <artifactId>flowable-spring-bo
spring boot 集成 flowable 报错 java.lang.ClassNotFoundException: liquibase.database.jvm.JdbcConnection
zhenye1986的专栏
10-25 4179
最近在折腾spring boot + flowable， 按照文档一步一步走，结果启动就报错： . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | ||...
flowable 6.2.1 初始化 oracle数据库表时失败的解决办法
01-23 8103
在使用flowable 创建初始化oracle数据表，出现如下错误： org.apache.ibatis.exceptions.PersistenceException: ### Error querying database. Cause: java.sql.SQLException: ORA-00942: 表或视图不存在 ### The error may exist in org/fl
java.lang.null_java.lang.NullPointerException: null
weixin_42360788的博客
02-12 852
有没有人遇到启动报空指针错误的？java.lang.NullPointerException: nullat org.flowable.engine.impl.db.ProcessDbSchemaManager.dbSchemaUpdate(ProcessDbSchemaManager.java:186)at org.flowable.engine.impl.db.ProcessDbSchemaM...
Springboot接入Activiti7
邢慧鹏的博客
03-10 2307
最近新项目要用工作流，查了几天资料，主要集中在 Activiti7、Flowable、Camunda 三个，同是 jbpm 框架发展而来，各有优劣。最终选择了Activiti7，原因无他，仅是手头参与的其他项目用这个，方便尽快上手，下个项目应该会试试另外两个。 ......
Flowable 6.6.0 事件注册表用户指南 - 4 Spring集成
月满闲庭的博客
01-07 438
4 Spring集成 While you can definitely use the Flowable Event Registry without Spring, we’ve provided some very nice integration features that are explained in this chapter. 虽然您完全可以在没有Spring的情况下使用Flowable事件注册表，但我们提供了一些非常好的集成特性，这些特性将在本章中解释。 4.1 EventRegistryFa
Flowable工作流入门
最新发布
摸魚散人的博客
01-04 1602
flowable流程引擎会将XML文件存储在数据库中，这样可以在需要的时候获取它流程定义转换为内部的、可执行的对象模型，这样使用它就可以启动流程实例。将下面的XML保存在文件夹下名为的文件中。
flowable exception during resetting expired jobs: Could not open JDBC Connection for transaction
Elena_00的博客
06-23 782
项目中遇到的一个问题，记录一下：项目中引入flowable后，生产环境运行一段时间后，出现了奇怪的问题， [flowable-bpmn-reset-expired-jobs] org.flowable.job.service.impl.asyncexecutor.ResetExpiredJobsRunnable.resetJobs - exception during resetting expired jobs: Could not open JDBC Connection for transactio
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springfr
热门推荐
Angela_L的博客
05-25 5万+
今天写springboot的项目时报错： Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled. 2019-05-25 10:55:33.996 ERROR 2748 --- [ main] ...
Flowable工作流数据库迁移及问题记录
FengChSvip的博客
12-24 853
工作流数据库数据迁移问题记录
Springboot+flowable6.6.0 流程引擎应用
猫七姑娘的小博客
11-30 7467
Springboot项目应用流程引擎 项目中要用到流程引擎，以前做项目是自己扣摸着做的简版引擎，现在工作中有机会要用流程引擎，就把他写成专题，记录下。 目录 Springboot项目应用流程引擎 一、部署flowable。 二、画流程图，在线生成流程xml配置文件。 三、接入项目。 一、部署flowable。 flowable部署见文章：https://blog.csdn.net/u013972652/article/details/109990809 ...
flowable自动建表失败Table ‘mes_design_test.act_ge_property‘ doesn‘t exist
Valhalla6416的博客
05-26 1994
flowable没有自动建表，错误内容： 2022-05-26 09:27:59.791 ERROR 170048 --- [ main] o.f.c.e.impl.db.CommonDbSchemaManager : Could not get property from table ACT_GE_PROPERTY java.sql.SQLSyntaxErrorException: Table 'mes_design_test.act_ge_property' doesn'
springboot 整合flowable-ui项目
12-28
Spring Boot是一个用于构建企业级应用的框架，而Flowable是一个轻量级的业务流程管理工具。在整合Spring Boot和Flowable-UI项目时，可以使用Spring Boot的自动配置功能来快速集成Flowable-UI项目并启动流程管理应用。 首先，需要在Spring Boot的pom.xml中加入Flowable-UI的依赖，并在application.properties中配置Flowable数据库的连接信息。然后通过编写一个启动类，通过@EnableAutoConfiguration注解来启用Spring Boot的自动配置功能，同时在该类中创建Flowable的各种服务、引擎和实例。 在代码中，可以使用Flowable提供的API来创建、启动和管理业务流程，同时也可以自定义Flowable的流程图、表单和任务处理逻辑。另外，还可以利用Flowable-UI项目提供的用户界面来实现流程的监控和管理，包括流程定义、任务分配、流程实例跟踪等功能。 通过整合Spring Boot和Flowable-UI项目，可以快速构建一个企业级的业务流程管理应用，并且利用Spring Boot提供的特性来简化配置、管理和监控流程应用。同时，通过Flowable-UI项目提供的界面，可以方便地实现用户与业务流程的交互和管理，从而提高企业的业务处理效率和质量。最终可以实现高效的业务流程管理和自动化，提升企业的竞争力和运营效率。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值