Flowable工作流启动错误：java.sql.SQLSyntaxErrorException: Table ‘act_ge_property‘ doesn‘t exist

最新推荐文章于 2024-04-29 15:43:08 发布
最新推荐文章于 2024-04-29 15:43:08 发布
阅读量301 收藏 1
点赞数 2
分类专栏： spring MySQL 文章标签： java 开发语言
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_37945670/article/details/137600726
版权

在使用工作流的情况下遇到以下的情况，应该是工作流初始化数据库的问题：

java.sql.SQLSyntaxErrorException: Table 'sitian-system-stage.act_ge_property' doesn't exist
	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:121)
	at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
	at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:916)
	at com.mysql.cj.jdbc.ClientPreparedStatement.executeQuery(ClientPreparedStatement.java:972)
	at com.alibaba.druid.filter.FilterChainImpl.preparedStatement_executeQuery(FilterChainImpl.java:3241)
	at com.alibaba.druid.filter.FilterEventAdapter.preparedStatement_executeQuery(FilterEventAdapter.java:459)
	at com.alibaba.druid.filter.FilterChainImpl.preparedStatement_executeQuery(FilterChainImpl.java:3238)
	at com.alibaba.druid.proxy.jdbc.PreparedStatementProxyImpl.executeQuery(PreparedStatementProxyImpl.java:175)
	at com.alibaba.druid.pool.DruidPooledPreparedStatement.executeQuery(DruidPooledPreparedStatement.java:213)
	at org.flowable.common.engine.impl.db.AbstractSqlScriptBasedDbSchemaManager.getProperty(AbstractSqlScriptBasedDbSchemaManager.java:202)
	at org.flowable.common.engine.impl.db.ServiceSqlScriptBasedDbSchemaManager.getSchemaVersion(ServiceSqlScriptBasedDbSchemaManager.java:116)
	at org.flowable.common.engine.impl.db.ServiceSqlScriptBasedDbSchemaManager.schemaUpdate(ServiceSqlScriptBasedDbSchemaManager.java:72)
	at org.flowable.common.engine.impl.db.ServiceSqlScriptBasedDbSchemaManager.schemaUpdate(ServiceSqlScriptBasedDbSchemaManager.java:65)
	at org.flowable.eventregistry.impl.db.EventDbSchemaManager.schemaUpdate(EventDbSchemaManager.java:62)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at org.flowable.common.engine.impl.db.LiquibaseBasedSchemaManager.runForLiquibase(LiquibaseBasedSchemaManager.java:93)
	at org.flowable.common.engine.impl.db.LiquibaseBasedSchemaManager.initSchema(LiquibaseBasedSchemaManager.java:81)
	at org.flowable.eventregistry.impl.db.EventDbSchemaManager.initSchema(EventDbSchemaManager.java:36)
	at org.flowable.eventregistry.impl.cmd.SchemaOperationsEventRegistryEngineBuild.execute(SchemaOperationsEventRegistryEngineBuild.java:29)
	at org.flowable.eventregistry.impl.cmd.SchemaOperationsEventRegistryEngineBuild.execute(SchemaOperationsEventRegistryEngineBuild.java:24)
	at org.flowable.common.engine.impl.interceptor.DefaultCommandInvoker.execute(DefaultCommandInvoker.java:22)
	at org.flowable.common.engine.impl.interceptor.TransactionContextInterceptor.execute(TransactionContextInterceptor.java:53)
	at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:105)
	at org.flowable.common.spring.SpringTransactionInterceptor.lambda$execute$0(SpringTransactionInterceptor.java:57)
	at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)
	at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:57)
	at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
	at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
	at org.flowable.eventregistry.impl.EventRegistryEngineImpl.<init>(EventRegistryEngineImpl.java:47)
	at org.flowable.eventregistry.impl.EventRegistryEngineConfiguration.buildEventRegistryEngine(EventRegistryEngineConfiguration.java:208)
	at org.flowable.eventregistry.spring.SpringEventRegistryEngineConfiguration.buildEventRegistryEngine(SpringEventRegistryEngineConfiguration.java:73)
	at org.flowable.eventregistry.spring.configurator.SpringEventRegistryConfigurator.initEventRegistryEngine(SpringEventRegistryConfigurator.java:57)
	at org.flowable.eventregistry.spring.configurator.SpringEventRegistryConfigurator.configure(SpringEventRegistryConfigurator.java:47)
	at org.flowable.common.engine.impl.AbstractEngineConfiguration.configuratorsAfterInit(AbstractEngineConfiguration.java:1120)
	at org.flowable.engine.impl.cfg.ProcessEngineConfigurationImpl.init(ProcessEngineConfigurationImpl.java:1022)
	at org.flowable.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:906)
	at org.flowable.spring.SpringProcessEngineConfiguration.buildProcessEngine(SpringProcessEngineConfiguration.java:76)
	at org.flowable.spring.ProcessEngineFactoryBean.getObject(ProcessEngineFactoryBean.java:59)
	at org.flowable.spring.ProcessEngineFactoryBean.getObject(ProcessEngineFactoryBean.java:32)
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:169)
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:101)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1898)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.getObjectForBeanInstance(AbstractAutowireCapableBeanFactory.java:1284)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:345)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1391)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311)
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:911)
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:788)
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:536)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1352)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1195)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1391)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.autowireResource(CommonAnnotationBeanPostProcessor.java:544)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.getResource(CommonAnnotationBeanPostProcessor.java:520)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:673)
	at org.springframework.beans.factory.annotation.InjectionMetadata$InjectedElement.inject(InjectionMetadata.java:228)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessProperties(CommonAnnotationBeanPostProcessor.java:329)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1391)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.autowireResource(CommonAnnotationBeanPostProcessor.java:544)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.getResource(CommonAnnotationBeanPostProcessor.java:520)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:673)
	at org.springframework.beans.factory.annotation.InjectionMetadata$InjectedElement.inject(InjectionMetadata.java:228)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
	at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessProperties(CommonAnnotationBeanPostProcessor.java:329)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:955)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:929)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:591)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:409)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:308)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1289)
	at com.wuqihuyu.sitian.manage.server.SitianServerApplication.main(SitianServerApplication.java:24)

询问ChatGPT + Google之后得到以下答案：

原因是mysql版本问题，mysql8会出现这个问题
因为mysql使用schema标识库名而不是catalog，因此mysql会扫描所有的库来找表，如果其他库中有相同名称的表，activiti就以为找到了，本质上这个表在当前数据库中并不存在。
设置nullCatalogMeansCurrent=true，表示mysql默认当前数据库操作，在mysql-connector-java 5.xxx该参数默认为true，在6.xxx以上默认为false，因此需要设置nullCatalogMeansCurrent=true。

修复之后：

          url: jdbc:mysql://192.168.1.69:3310/${spring.datasource.dynamic.datasource.master.name}?useSSL=false&serverTimezone=Asia/Shanghai&allowPublicKeyRetrieval=true&characterEncoding=utf8&nullCatalogMeansCurrent=true
          driver-class-name: com.mysql.jdbc.Driver
          username: sitian
          password: 123456

然后就可以启动成功了

XuanRanDev
关注
  • 2
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Flowable删表问题之table ‘activiti.act_ge_property‘ doesn‘t exist
qq_34149223的博客
12-24 2214
1.问题产生的原因： 由于自己采用的是mysql5.7版本且未做过多的配置，flowable自动生成的表全部是大写，个人不太习惯，就在把flowable在mysql中多对应的schema（数据库）中的表全部删除，然后在my.cfg（windows可能是my.ini）这些配置文件中加入限定表为小写的配置（在[mysqld]下加入lower_case_table_names=1，重启mysql服务）。 然后启动项目，结果出现 问题： org.apache.ibatis.exceptions.Persistenc
jeesite 框架，在启动运行时报错 Table'ACT_GE_PROPERTY' not exist 解决方法
wangxi_xixi的博客
09-11 7913
问题描述： jeesite 框架，在启动运行时报错 ACT_GE_PROPERTY 这张表不存在，看了一下数据库发现表中的这张表名为act_ge_property。 解决办法： 可以在MySQL my.ini文件的[mysqld] 下面添加一行 ：lower_case_table_names=1，再重启MySQL。 或者可以修改spring-context-activiti.xml这个文件...
解决activiti java.sql.SQLSyntaxErrorException: Table ‘activit.ACT_GE_PROPERTY‘ doesn‘t exist
最新发布
weixin_52293201的博客
04-29 346
在数据库链接 url后加上 nullCatalogMeansCurrent=true，再次执行@Test方法，运行，即可看到成功生成了25张表！查阅资料后，终于找到了解决办法！
Flowable深入浅出-6 Flowable-Modeler详述之常见问题Table act_ge_property doesn‘t exist
热门推荐
Full in love with code
01-01 1万+
6 Flowable-Modeler详述之常见问题Table act_ge_property doesn't exist问题描述问题定位解决方案一解决方案二(推荐)验证结果打赏版权 问题描述 在配置完Springboot的开发环境以后，启动的时候遇到了这个问题，数据库版本为mysql 5.7,Flowable版本为6.4.0，详细报错如下： org.springframework.beans.fa...
Table 'ACT_GE_PROPERTY' doesn't exist，version mismatch: library version is '6.5.0.1', db version is
止境博客
10-12 4168
1.使用mysql初始化Flowable数据库出现Table 'guns.ACT_GE_PROPERTY' doesn't exist可以在数据库连接中加入下面参数 nullCatalogMeansCurrent=true 因为机器上以前其他的mysql数据库中部署过Flowable的表，所以当schema为空的时候搜索mysql的元数据的时候搜索到了历史用的表，但是不在该数据库中，所以程序...
flowable 6.6.0 java.sql.SQLSyntaxErrorException: Table ‘act_ge_property‘ doesn‘t exist
qq_36213455的博客
06-12 1336
spring.datasource.url=jdbc:mysql://127.0.0.1:3306/flowable?useUnicode=true&characterEncoding=utf-8&useSSL=true&nullCatalogMeansCurrent=true&serverTimezone=UTC
jeecg activity 集成报错 Table act_ge_property doesn‘t exist
yeyuangongzuoshi的博客
06-17 1092
Table act_ge_property doesn't exist 加入这句话到链接url那里： url: jdbc:mysql://127.0.0.1:3306/jeecg-boot?characterEncoding=UTF-8&useUnicode=true&useSSL=false&tinyInt1isBit=false&nullCatalogMeansCurrent=true&allowPublicKeyRetrieval=true&serv
act_de_table.sql
03-09
flowable-modeler在6.4.1版后不用act_re_model表来保存流程模型文件，改为用act_de_model表来保存，但是有的版本启动后act_de前缀表没有自动创建；附件中共享了act_de前缀的表，希望对大家有用；
flowable.mysql.all.create.sql
10-27
sql
OA办公系统 Springboot vue.js前后分离，Flowable工作流自定义表单
04-09
特别注意:本商品为 Springboot 工作流 前后分离+跨域 版本 (权限控制到菜单和按钮) 后台框架:springboot 2.7.0+Flowable6.7.2+ mybaits+maven+接囗前端页面:html +vuejs 形式jquery ajax 异步跨域json 格式数据交互 ...
flowable工作流.zip
01-03
对flowable工作流的简单的学习总结，包括flowable的简介、使用，和spring、sprinboot的整合，一些常见场景的解决方案
SpringBoot2.7集成flowable最新版，java工作流服务端实现，解耦设计
02-28
# 基于原生flowable实现的流程引擎 本项目基于最新6.8.0的flowable，使用最新springboot集成。文档请联系作者索要。...单独启动项目后，通过配套的sdk调用官方接口，就能够完成工作流的快速接入，轻量解耦。
Activiti流创建数据表的过程中报错 java.sql.SQLSyntaxErrorException: Table ‘activiti.act_ge_property‘ doesn‘t exis
3927的博客
06-26 1143
Activiti流创建数据表的过程中报错 java.sql.SQLSyntaxErrorException: Table 'activiti.act_ge_property' doesn't exist
Activiti 初始化启动失败提示 ACT_GE_PROPERTY 表不存在
Mrqiang9001
07-21 1万+
文章目录1 问题描述2 解决办法3 参考资料 1 问题描述 启动 Activiti 项目时，会执行数据库的检查以及初始化操作，数据库中没有对应的 activiti 数据库表，程序没有自动创建，并提示表不存在。 数据库为 MySQL 5.7+ 具体报错如下: java.sql.SQLSyntaxErrorException: Table 'demo_activiti.ACT_GE_PROPERTY' doesn't exist ​ 2 解决办法 在 MySQL 的链接 URL 中添加: nullCatalo
flowable项目报错:java.sql.SQLSyntaxErrorException: Table ‘psr_flowable_test.act_ge_property’ doesn’t exi
流楚丶格念的博客
09-07 1166
【代码】flowable项目报错:java.sql.SQLSyntaxErrorException: Table ‘psr_flowable_test.act_ge_property’ doesn’t exi。
Flowable 数据库表结构 ACT_GE_PROPERTY
Gblfy_Blog
04-03 768
属性数据表(act_ge_property) 属性数据表。存储整个流程引擎级别的数据 字段名称 字段描述 数据类型 主键 为空 取值说明 NAME_ 名称 nvarchar(64) √ schema.versionschema.historynext.dbid VALUE_ 值 nvarchar(300) √ 5.create(5.) REV_ 乐观锁 int √ version ...
工作流Flowable启动错误：解决 Could not get property from table ACT_GE_PROPERTY
tanxvyang的博客
09-26 634
Flowable，mysql8.xxx，配置，nullCatalogMeansCurrent=true
flowable启动时报错
smileLs的博客
06-20 3484
flowable启动报错
Flowable 6.6.0 事件注册表用户指南 - 2 配置 - 2.2、2.3
月满闲庭的博客
01-06 674
2.2 EventRegistryEngineConfiguration bean The flowable.eventregistry.cfg.xml must contain a bean that has the ID ‘eventRegistryEngineConfiguration’. flowable.eventregistry.cfg.xml文件必须包含ID为“eventRegistryEngineConfiguration”的bean。 <bean id="eventRegistry
Caused by: java.sql.SQLSyntaxErrorException: Unknown database 'flowable' at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:121) at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) at com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:763) at com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:648) at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:94) at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:393) ... 104 common frames omitted
06-07
根据错误信息，可以看出是在执行 SQL 语句时出现了错误，具体来说是关于 `flowable` 数据库的错误。错误信息中显示 `Unknown database 'flowable'`，说明该数据库不存在或无法访问。这可能是由于以下原因导致的： 1. 数据库未正确安装：如果您尚未安装 `flowable` 数据库，则需要先安装它。请确保您已按照流程正确安装了数据库，并且数据库已启动。 2. 数据库连接配置错误：如果您已经安装了 `flowable` 数据库，则需要检查数据库连接配置是否正确。请检查您的数据库连接字符串、用户名和密码是否正确，并确保您正在连接到正确的数据库。 3. 数据库权限问题：如果您已经安装了 `flowable` 数据库并且连接配置正确，则需要检查您是否具有访问 `flowable` 数据库的权限。请确保您的数据库用户具有足够的权限来访问该数据库。 4. 数据库版本问题：如果您的 `flowable` 版本与数据库不兼容，则可能会导致该错误。请确保您的 `flowable` 版本与数据库版本兼容，并且您已正确配置了数据库。 为了解决这个问题，您可以尝试以下几步： 1. 确保已正确安装 `flowable` 数据库，并且数据库已启动。 2. 检查您的数据库连接配置是否正确，并确保您连接到了正确的数据库。 3. 检查您是否具有访问 `flowable` 数据库的权限。 4. 确保您的 `flowable` 版本与数据库版本兼容，并且您已正确配置了数据库。 如果以上步骤都没有解决问题，您可以尝试使用调试工具来进一步分析错误。可以在代码中添加日志或使用断点调试器来了解程序的执行流程和变量状态。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值