精华内容
下载资源
问答
  • yml 添加下面的配置,显示activiti操作数据库的SQL日志: logging: level: org.activiti.engine.impl.persistence.entity: debug properties 配置: logging.level.org.activiti.engine.impl.persistence....

    yml 添加下面的配置,显示activiti操作数据库的SQL日志: 

    logging:
      level:
        org.activiti.engine.impl.persistence.entity: debug

     

    properties 配置:

    logging.level.org.activiti.engine.impl.persistence.entity=debug

     

    展开全文
  • springboot打印activitisql日志

    千次阅读 2018-12-18 14:26:06
    logback.xml配置文件中配置activitisql日志打印: 在logback.xml配置文件中增加如下配置: <!-- Activiti日志 --> <logger name="org.activiti" level="ERROR" /> <logger name="org.activiti.engine.impl....
    logging:
      level:
        com.len.mapper: DEBUG
        org.activiti.engine.impl.persistence.entity: trace
    

    在这里插入图片描述

    2018-12-18 14:46:31.497 DEBUG 24380 --- [nio-8080-exec-1] lectDeploymentCountByQueryCriteria_mysql : ==>  Preparing: select distinct count(RES.ID_) from ACT_RE_DEPLOYMENT RES 
    2018-12-18 14:46:31.497 DEBUG 24380 --- [nio-8080-exec-1] lectDeploymentCountByQueryCriteria_mysql : ==> Parameters: 
    2018-12-18 14:46:31.499 TRACE 24380 --- [nio-8080-exec-1] lectDeploymentCountByQueryCriteria_mysql : <==    Columns: count(RES.ID_)
    2018-12-18 14:46:31.500 TRACE 24380 --- [nio-8080-exec-1] lectDeploymentCountByQueryCriteria_mysql : <==        Row: 2
    2018-12-18 14:46:31.500 DEBUG 24380 --- [nio-8080-exec-1] lectDeploymentCountByQueryCriteria_mysql : <==      Total: 1
    2018-12-18 14:47:08.098 DEBUG 24380 --- [nio-8080-exec-4] com.len.mapper.SysUserMapper.login       : ==>  Preparing: select id, username, password, age, email, photo, real_name, create_by, update_by, create_date, update_date, del_flag from sys_user where username=? 
    2018-12-18 14:47:08.099 DEBUG 24380 --- [nio-8080-exec-4] com.len.mapper.SysUserMapper.login       : ==> Parameters: tom(String)
    2018-12-18 14:47:08.100 DEBUG 24380 --- [nio-8080-exec-4] com.len.mapper.SysUserMapper.login       : <==      Total: 1
    2018-12-18 14:47:08.101 DEBUG 24380 --- [nio-8080-exec-4] c.len.mapper.SysMenuMapper.getUserMenu   : ==>  Preparing: select m.*,r.id as rid,r.role_name as role_name,r.remark as remark from sys_menu m left join sys_role_menu rm on m.id=rm.menu_id left join sys_role r on rm.role_id=r.id left join sys_role_user ru on r.id=ru.role_id where ru.user_id =? order by m.order_num asc 
    2018-12-18 14:47:08.101 DEBUG 24380 --- [nio-8080-exec-4] c.len.mapper.SysMenuMapper.getUserMenu   : ==> Parameters: 2211fec3e17c11e795ed201a068c6482(String)
    2018-12-18 14:47:08.117 DEBUG 24380 --- [nio-8080-exec-4] c.len.mapper.SysMenuMapper.getUserMenu   : <==      Total: 9
    2018-12-18 14:47:08,118:INFO ========http-nio-8080-exec-4 (LoginController.java:108) - 用户:tom,登陆成功,ip:0:0:0:0:0:0:0:1
    2018-12-18 14:47:13.515 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.G.selectGroupsByUserId       : ==>  Preparing: select g.* from ACT_ID_GROUP g, ACT_ID_MEMBERSHIP membership where g.ID_ = membership.GROUP_ID_ and membership.USER_ID_ = ? 
    2018-12-18 14:47:13.517 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.G.selectGroupsByUserId       : ==> Parameters: 2211fec3e17c11e795ed201a068c6482(String)
    2018-12-18 14:47:13.521 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.e.G.selectGroupsByUserId       : <==    Columns: ID_, REV_, NAME_, TYPE_
    2018-12-18 14:47:13.521 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.e.G.selectGroupsByUserId       : <==        Row: 0ea934e5e55411e7b983201a068c6482, 1, manage, null
    2018-12-18 14:47:13.522 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.G.selectGroupsByUserId       : <==      Total: 1
    2018-12-18 14:47:13.525 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.T.selectTaskByQueryCriteria  : ==>  Preparing: select distinct RES.* from ACT_RU_TASK RES inner join ACT_RU_IDENTITYLINK I on I.TASK_ID_ = RES.ID_ WHERE RES.ASSIGNEE_ is null and I.TYPE_ = 'candidate' and ( I.USER_ID_ = ? or I.GROUP_ID_ IN ( ? ) ) order by RES.ID_ asc LIMIT ? OFFSET ? 
    2018-12-18 14:47:13.526 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.T.selectTaskByQueryCriteria  : ==> Parameters: 2211fec3e17c11e795ed201a068c6482(String), 0ea934e5e55411e7b983201a068c6482(String), 2147483647(Integer), 0(Integer)
    2018-12-18 14:47:13.528 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.e.T.selectTaskByQueryCriteria  : <==    Columns: ID_, REV_, EXECUTION_ID_, PROC_INST_ID_, PROC_DEF_ID_, NAME_, PARENT_TASK_ID_, DESCRIPTION_, TASK_DEF_KEY_, OWNER_, ASSIGNEE_, DELEGATION_, PRIORITY_, CREATE_TIME_, DUE_DATE_, CATEGORY_, SUSPENSION_STATE_, TENANT_ID_, FORM_KEY_
    2018-12-18 14:47:13.528 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.e.T.selectTaskByQueryCriteria  : <==        Row: 35013, 1, 35005, 35005, process_leave:2:35004, 经理审批, null, null, manager, null, null, null, 50, 2018-12-18 14:43:39.0, null, null, 1, , null
    2018-12-18 14:47:13.528 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.T.selectTaskByQueryCriteria  : <==      Total: 1
    2018-12-18 14:47:13.530 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.entity.TaskEntity.selectTask   : ==>  Preparing: select * from ACT_RU_TASK where ID_ = ? 
    2018-12-18 14:47:13.530 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.entity.TaskEntity.selectTask   : ==> Parameters: 35013(String)
    2018-12-18 14:47:13.555 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.entity.TaskEntity.selectTask   : <==    Columns: ID_, REV_, EXECUTION_ID_, PROC_INST_ID_, PROC_DEF_ID_, NAME_, PARENT_TASK_ID_, DESCRIPTION_, TASK_DEF_KEY_, OWNER_, ASSIGNEE_, DELEGATION_, PRIORITY_, CREATE_TIME_, DUE_DATE_, CATEGORY_, SUSPENSION_STATE_, TENANT_ID_, FORM_KEY_
    2018-12-18 14:47:13.555 TRACE 24380 --- [io-8080-exec-10] o.a.e.i.p.entity.TaskEntity.selectTask   : <==        Row: 35013, 1, 35005, 35005, process_leave:2:35004, 经理审批, null, null, manager, null, null, null, 50, 2018-12-18 14:43:39.0, null, null, 1, , null
    2018-12-18 14:47:13.555 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.entity.TaskEntity.selectTask   : <==      Total: 1
    2018-12-18 14:47:13.555 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.V.selectVariablesByTaskId    : ==>  Preparing: select * from ACT_RU_VARIABLE where TASK_ID_ = ? 
    2018-12-18 14:47:13.556 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.V.selectVariablesByTaskId    : ==> Parameters: 35013(String)
    2018-12-18 14:47:13.557 DEBUG 24380 --- [io-8080-exec-10] o.a.e.i.p.e.V.selectVariablesByTaskId    : <==      Total: 0
    

    logback.xml配置文件中配置activiti的sql日志打印:
    在logback.xml配置文件中增加如下配置:

    <!-- Activiti日志 -->
    	<logger name="org.activiti" level="ERROR" />
    	<logger name="org.activiti.engine.impl.persistence.entity" level="DEBUG" />
    
    
    展开全文
  • Activiti开启打印SQL查询日志

    万次阅读 2018-03-16 18:47:37
    开启activiti sql查询日志 在log4j.properties中加入如下配置 log4j.logger.org.activiti.engine.impl.persistence.entity=trace 重启,显示效果如图:

    开启activiti sql查询日志
    在log4j.properties中加入如下配置
    log4j.logger.org.activiti.engine.impl.persistence.entity=trace

    重启,显示效果如图:
    这里写图片描述

    展开全文
  • 项目是Springboot+activiti+log4j+gradle 1.配置log4j.properties 网上很多,随便copy个就行 ...//日志级别是debug才能显示SQL日志,info是不显示的 logging.level.root=debug logging.level.org.springframewo...

    项目是Springboot+activiti+log4j+gradle

    1.配置log4j.properties

    网上很多,随便copy个就行

    2.配置application.properties,添加一下代码:

    //日志级别是debug才能显示SQL日志,info是不显示的
    logging.level.root=debug
    logging.level.org.springframework.web=error
    logging.level.org.hibernate=ERROR

    3.修改grdle配置文件:

        compile('org.slf4j:slf4j-api:1.7.5')
        compile('ch.qos.logback:logback-classic:1.2.3')
    
        compile 'org.springframework.boot:spring-boot-starter-log4j:1.3.8.RELEASE'
        

    若是maven项目,在pom文件中加入以上三个依赖就可以

    完毕。

    展开全文
  • Activiti6 打印内置sql

    2020-12-16 10:02:59
    # 日志配置 logging: level: com.ruoyi: debug # com.ruoyi: trace org.springframework: warn #打印sql org.activiti.engine.impl.persistence.entity: trace
  • activiti打印mybatis的sql

    2016-06-09 15:54:06
    logback配置 ... <pattern>%d{HH:mm:ss.SSS}...-- show activiti sql--> <logger name="org.activiti.engine.impl.persistence.entity" level="DEBUG" /> <!--<appender-ref ref="FILE" />-->
  • Activiti不能打印日志问题

    千次阅读 2018-04-10 12:05:34
    分享知识 传递快乐在使用Activiti工作流时不能打印日志问题:引入日志的方式基本上有两种:一种用log4j.properties;另一种用logback.xml配置。引用了log4j.properties式的日志功能,那么当加入activiti工作流时,在...
  • 根据日志执行mysql的日志,推执行逻辑 根据日志执行mysql的日志,推执行逻辑 1.ACT_GE_PROPERTY 查看系统配置表 1 2.ACT_RU_TASK 查询当前任务表 1 3.ACT_RU_VARIABLE 查询系统变量表 0 4.ACT_RE_PROCDEF 查询流程...
  • 目的是通过activiti打印SQL日志,来分析对activiti的操作涉及到了哪些表; logging.level.org.activiti.engine.impl.persistence.entity=debug 如果启动项目后,你会发现,会不停的打印查询SQL日志: #在流程引擎...
  • activity打印sql

    2020-04-16 15:56:25
    log4j.logger.org.activiti.engine.impl.persistence.entity=trace
  • 解决activiti6一直查询sql问题

    千次阅读 2018-04-16 13:27:32
    启动项目 控制台一直打印如下sql (间隔10s打印一次)select RES.* from ACT_RU_TIMER_JOB RES where DUEDATE_ &lt;= '2018-04-16 13:21:26' and LOCK_OWNER_ select RES.* from ACT_RU_JOB RES where LOCK_...
  • :47:43.617 [activiti-acquire-async-jobs] DEBUG o.a.e.i.p.e.J.selectJobsToExecute - [debug,159] - ==> Preparing: select RES.* from ACT_RU_JOB RES where LOCK_EXP_TIME_ is null LIMIT ? OFFSET ? 15:47...
  • Activiti

    千次阅读 2017-05-01 21:58:37
    关于学习Activiti的过程:直接使用官方文档进行学习,希望会有好的效果。 一.首先是现在官方的包,在其中拿到activiti-explorer.war包,将其部署到tomcate下进行访问,看看需要新学习的是一个什么东东。了解一个大概...
  • activiti

    2018-09-07 11:24:00
    Activiti框架提供了sql脚本文件用于建表,这些sql脚本文件就位于Activiti框架database目录下的create目录中,如下:  下面我就来使用Activiti框架提供的sql脚本建表,步骤如下:  【第一步】,手动创建一个数据库...
  • #--------打印sql语句--------------------#  #\u9996\u5148\u5C06rootLogger\u7EA7\u522B\u66F4\u6539\u4E3ADEBUG #1 \u5B9A\u4E49\u65E5\u5FD7\u8F93\u51FA\u76EE\u7684\u5730\u4E3A\u63A7\u5236\u53F0 ...
  • <logger name="org.activiti.engine" level="ERROR" additivity="false"> level="ERROR" additivity="false"> <!-- 日志输出级别 ...
  • Spring-boot--打印sql参数 log4jdbc与logback配置   在开发过程中,常常需要验证sql语句,但是spring-boot-starter-data-jpa只支持输出sql不会输出参数,为了方便,集成log4jdbc。 一、引入依赖 &lt;...
  • Activiti学习笔记一:创建数据库表

    千次阅读 2016-08-28 21:03:41
    解压activiti压缩包,找到sql文件手动执行。 二、通过代码执行// 使用代码创建activiti需要的23个表 @Test public void creteTable() { ProcessEngineConfiguration processEngineConfiguration = ...
  • Activiti使用

    2020-02-19 22:02:17
    Activiti课件 工作流的概念 说明: 假设:这两张图就是华谊兄弟的请假流程图 图的组成部分: 人物:范冰冰 冯小刚 王中军 事件(动作):请假、批准、不批准 工作流(Workflow),就是“业务过程的...
  • Activiti工作流配置创建ProcessEngineProcessEngineConfiguration bean数据库配置定义数据库配置参数使用javax.sql.DataSource配置JNDI数据库配置JNDI的使用JNDI的配置Activiti支持的数据库创建数据库表数据库表名...
  • 工作流Activiti

    2018-07-15 09:13:59
    Activiti工作流一:Activiti 一1:工作流的概念  说明:1) 假设:这两张图就是华谊兄弟的请假流程图2) 图的组成部分:A. 人物:范冰冰 冯小刚 王中军B. 事件(动作):请假、批准、不批准  工作流(Workflow)...
  • activiti笔记

    2016-06-06 17:04:34
    打开菜单Windows->Preferences->Activiti->Save下流程流程图片的生成方式: 虽然流程引擎在单独部署bpmn文件时会自动生成图片,但在实际开发过程中,自动生成的图片会导致和BPMN中的坐标有出入,在实际...
  • Activiti工作流

    2019-10-18 21:29:24
    Activiti工作流 目录 Activiti工作流 1 概述 2Activiti介绍 工作流引擎 BPMN 数据库 activiti.cfg.xml(activiti的配置文件) 自己项目中的配置 logging...
  • Activiti教程

    2020-08-19 18:29:28
      jdbcMaxWaitTime: 这是一个底层配置,让连接池可以在长时间无法获得连接时, 打印一条日志,并重新尝试获取一个连接。(避免因为错误配置导致沉默的操作失败)。 默认为20000(20秒)。 示例数据库配置: 也...
  • MDC记录activiti流程ID

    2018-10-11 16:40:03
    一.自定义 MDCCommandInvoker 拦截器类 继承 DebugCommandInvoker 重写方法:executeOperation package interceptor; import org.activiti.engine.debug....import org.activiti.engine.impl.agenda.Abstract...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 440
精华内容 176
关键字:

activiti打印sql日志