Shulou(Shulou.com)06/01 Report--

The isEngineTablePresent judgment logic is as follows:

Public boolean isEngineTablePresent () {return isTablePresent ("ACT_RU_EXECUTION");}

The core code uses the getTables method of jdbc to judge.

Because the Flowable project was deployed in the mysql database, the table was deleted when the environment was built, so when schema is empty, the history table is searched when looking for the metadata of mysql. But not in the current connection database, the code logic thinks that the table already exists, but it is actually a historical table, and basically finds the reason.

The mysql version 8.0 driver changed the default value of the parameter nullCatalogMeansCurrent from true to false. If you use DatabaseMetaData.getTables to get all the table information, including historical table records, resulting in misjudgment.

Solution one

Export the table of the normal database to sql and create the table manually.

Solution two

Add nullCatalogMeansCurrent=true to the connection string of mysql and set it to check only the currently connected schema library.

Server: port: 8080spring: datasource: driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://127.0.0.1:3306/flowable?characterEncoding=UTF-8&serverTimezone=UTC&useUnicode=true&useSSL=false&nullCatalogMeansCurrent=true username: root password: this is the answer to the question about how to analyze the Table 'flowable.act_ge_property' doesn't exist question of flowable workflow engine. I hope the above content can be of some help to you. If you still have a lot of questions to solve, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.