博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
JAVA常用工具【一】
阅读量:4578 次
发布时间:2019-06-08

本文共 12876 字,大约阅读时间需要 42 分钟。

java常用工具【一】

一:数据库访问操作动态监控–p6spy

P6Spy 是针对数据库访问操作的动态监测框架(为开源项目,项目地址为:)它使得数据库数据可无缝截取和操纵,而不必对现有应用程序的代码作任何修改。P6Spy 分发包包括P6Log,它是一 个可记录任何 Java 应用程序的所有JDBC事务的应用程序。其配置完成使用时,可以进行数据访问性能的监测。

使用p6spy我们可以直接查看到数据库执行的sql而不是预编译带?的SQL。
P6Spy通过劫持JDBC驱动,在调用实际JDBC驱动前拦截调用的目标语,达到SQL语句日志记录的目的


1:p6spy使用准备

p6spy的jar包spy.properties自定义日志格式修改相关配置文件

2:p6spy的使用

step1:添加依赖

p6spy
p6spy
3.6.0

step2:修改连接池或者连接配置的jdbc的驱动为p6spy所提供的保证后的驱动,com.p6spy.engine.spy.P6SpyDriver

#配置数据库连接信息#配置druidspring.datasource.type=com.alibaba.druid.pool.DruidDataSourcespring.datasource.driver-class-name=com.p6spy.engine.spy.P6SpyDriverspring.datasource.url=jdbc:p6spy:mysql:///k9_test?useSSL=falsespring.datasource.username=rootspring.datasource.password=root

step3:添加spy.properties

#### #%L# P6Spy# %%# Copyright (C) 2013 P6Spy# %%# Licensed under the Apache License, Version 2.0 (the "License");# you may not use this file except in compliance with the License.# You may obtain a copy of the License at# #      http://www.apache.org/licenses/LICENSE-2.0# # Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License.# #L%##################################################################### P6Spy Options File                                            ## See documentation for detailed instructions                   ## http://p6spy.github.io/p6spy/2.0/configandusage.html          #################################################################################################################################### MODULES                                                       ##                                                               ## Module list adapts the modular functionality of P6Spy.		## Only modules listed are active.						        ## (default is com.p6spy.engine.logging.P6LogFactory and         ## com.p6spy.engine.spy.P6SpyFactory)                            ## Please note that the core module (P6SpyFactory) can't be		# # deactivated. 													## Unlike the other properties, activation of the changes on     ## this one requires reload.										###################################################################modulelist=com.p6spy.engine.spy.P6SpyFactory,com.p6spy.engine.logging.P6LogFactory,com.p6spy.engine.outage.P6OutageFactory################################################################# CORE (P6SPY) PROPERTIES                                      ################################################################## A comma separated list of JDBC drivers to load and register.# (default is empty)## Note: This is normally only needed when using P6Spy in an# application server environment with a JNDI data source or when# using a JDBC driver that does not implement the JDBC 4.0 API# (specifically automatic registration).# mysql数据库驱动driverlist=com.mysql.jdbc.Driver# for flushing per statement# (default is false)autoflush = true# sets the date format using Java's SimpleDateFormat routine. # In case property is not set, miliseconds since 1.1.1970 (unix time) is used (default is empty)#dateformat=# prints a stack trace for every statement logged#stacktrace=false# if stacktrace=true, specifies the stack trace to print#stacktraceclass=# determines if property file should be reloaded# Please note: reload means forgetting all the previously set# settings (even those set during runtime - via JMX)# and starting with the clean table # (default is false)#reloadproperties=false# determines how often should be reloaded in seconds# (default is 60)#reloadpropertiesinterval=60# specifies the appender to use for logging# Please note: reload means forgetting all the previously set# settings (even those set during runtime - via JMX)# and starting with the clean table # (only the properties read from the configuration file)# (default is com.p6spy.engine.spy.appender.FileLogger)#appender=com.p6spy.engine.spy.appender.Slf4JLogger#打印到控制台appender=com.p6spy.engine.spy.appender.StdoutLogger#将程序执行的sql语句保存在单独的文件中去appender=com.p6spy.engine.spy.appender.FileLogger# name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) # (used for com.p6spy.engine.spy.appender.FileLogger only)# (default is spy.log)#logfile = D:\\spy.log# append to the p6spy log file. if this is set to false the# log file is truncated every time. (file logger only)# (default is true)#append=true# class to use for formatting log messages (default is: com.p6spy.engine.spy.appender.SingleLineFormat)#自定义日志格式,在类中定义默认的格式化方式为com.p6spy.engine.spy.appender.SingleLineFormat:我们可以将其替换为我们自定义的输出格式:#logMessageFormat=com.p6spy.engine.spy.appender.SingleLineFormatlogMessageFormat=com.zhylb.tools.P6SpyLogger# format that is used for logging of the date/time/... (has to be compatible with java.text.SimpleDateFormat)# (default is dd-MMM-yy)databaseDialectDateFormat=yyyy-MM-dd HH:mm:ss# whether to expose options via JMX or not# (default is true)#jmx=true# if exposing options via jmx (see option: jmx), what should be the prefix used?# jmx naming pattern constructed is: com.p6spy(.
)?:name=
# please note, if there is already such a name in use it would be unregistered first (the last registered wins)# (default is none)#jmxPrefix=################################################################## DataSource replacement ## ## Replace the real DataSource class in your application server ## configuration with the name com.p6spy.engine.spy.P6DataSource ## (that provides also connection pooling and xa support). ## then add the JNDI name and class name of the real ## DataSource here ## ## Values set in this item cannot be reloaded using the ## reloadproperties variable. Once it is loaded, it remains ## in memory until the application is restarted. ## ###################################################################realdatasource=/RealMySqlDS#realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource################################################################## DataSource properties ## ## If you are using the DataSource support to intercept calls ## to a DataSource that requires properties for proper setup, ## define those properties here. Use name value pairs, separate ## the name and value with a semicolon, and separate the ## pairs with commas. ## ## The example shown here is for mysql ## ###################################################################realdatasourceproperties=port;3306,serverName;myhost,databaseName;jbossdb,foo;bar################################################################## JNDI DataSource lookup ## ## If you are using the DataSource support outside of an app ## server, you will probably need to define the JNDI Context ## environment. ## ## If the P6Spy code will be executing inside an app server then ## do not use these properties, and the DataSource lookup will ## use the naming context defined by the app server. ## ## The two standard elements of the naming environment are ## jndicontextfactory and jndicontextproviderurl. If you need ## additional elements, use the jndicontextcustom property. ## You can define multiple properties in jndicontextcustom, ## in name value pairs. Separate the name and value with a ## semicolon, and separate the pairs with commas. ## ## The example shown here is for a standalone program running on ## a machine that is also running JBoss, so the JDNI context ## is configured for JBoss (3.0.4). ## ## (by default all these are empty) ###################################################################jndicontextfactory=org.jnp.interfaces.NamingContextFactory#jndicontextproviderurl=localhost:1099#jndicontextcustom=java.naming.factory.url.pkgs;org.jboss.nameing:org.jnp.interfaces#jndicontextfactory=com.ibm.websphere.naming.WsnInitialContextFactory#jndicontextproviderurl=iiop://localhost:900################################################################# P6 LOGGING SPECIFIC PROPERTIES ################################################################## filter what is logged# please note this is a precondition for usage of: include/exclude/sqlexpression# (default is false)#filter=false# comma separated list of strings to include# please note that special characters escaping (used in java) has to be done for the provided regular expression# (default is empty)#include =# comma separated list of strings to exclude# (default is empty)#exclude =# sql expression to evaluate if using regex# please note that special characters escaping (used in java) has to be done for the provided regular expression# (default is empty)#sqlexpression = #list of categories to exclude: error, info, batch, debug, statement,#commit, rollback and result are valid values# (default is info,debug,result,resultset,batch)#excludecategories=info,debug,result,resultset,batch# Execution threshold applies to the standard logging of P6Spy. # While the standard logging logs out every statement # regardless of its execution time, this feature puts a time # condition on that logging. Only statements that have taken # longer than the time specified (in milliseconds) will be # logged. This way it is possible to see only statements that # have exceeded some high water mark. # This time is reloadable. ## executionThreshold=integer time (milliseconds)# (default is 0)#executionThreshold=################################################################# P6 OUTAGE SPECIFIC PROPERTIES ################################################################## Outage Detection## This feature detects long-running statements that may be indicative of# a database outage problem. If this feature is turned on, it will log any# statement that surpasses the configurable time boundary during its execution.# When this feature is enabled, no other statements are logged except the long# running statements. The interval property is the boundary time set in seconds.# For example, if this is set to 2, then any statement requiring at least 2# seconds will be logged. Note that the same statement will continue to be logged# for as long as it executes. So if the interval is set to 2, and the query takes# 11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).## outagedetection=true|false# outagedetectioninterval=integer time (seconds)## (default is false)#outagedetection=false# (default is 60)#outagedetectioninterval=30

step4:创建P6SpyLogger类,自定义日志格式

package com.dmsd.tool;import com.p6spy.engine.spy.appender.MessageFormattingStrategy;import java.text.SimpleDateFormat;import java.util.Date;/** * p6spy打印日志输出格式修改 * 1.只打印最终执行的sql. * 2.sql换到下一行 * 3.结尾处增加分号,以标示sql结尾 * Created by odelia on 2016/1/4. */public class P6SpyLogger implements MessageFormattingStrategy {    private SimpleDateFormat format = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss:SSS");    public P6SpyLogger() {    }    @Override    public String formatMessage(int connectionId, String now, long elapsed, String category, String prepared, String sql) {        return !"".equals(sql.trim())?this.format.format(new Date()) + " | took " + elapsed + "ms | " + category + " | connection " + connectionId + "\n " + sql + ";":"";}}

step5:查看打印结果

2018-07-14 14:38:39.527  INFO 4088 --- [nio-8082-exec-1] p6spy                                    : 2018-07-14 14:38:39:527 | took 7ms | statement | connection 4select id, scorefrom a_innodb_testwhere id = 1;

转载地址:http://koqms.baihongyu.com/

你可能感兴趣的文章
Java 最简单的UPD Server
查看>>
Java使用OkHttps工具类调用外部接口
查看>>
C# Sftp操作
查看>>
刷题总结——保留道路(ssoj)
查看>>
CentOS下安装配置LAMP(Linux+Apache+MySQL+PHP)
查看>>
复制从文件初始化
查看>>
css3-4 css3边框样式
查看>>
office excel读写类NPOI
查看>>
Python学习笔记(二)--变量和数据类型
查看>>
MYSQL,DB2,SQLSERVER数据库不同点浅探(一)
查看>>
SVN创建分支/合并分支/切换分支
查看>>
突袭HTML5之SVG 2D入门5 - 颜色的表示
查看>>
HTML第七章
查看>>
mysql去除重复数据
查看>>
Freemarker导出带多个不重复图片的word
查看>>
windows 配置squid反向代理服务器
查看>>
Java知识系统回顾整理01基础03变量07final关键字
查看>>
js学习总结----crm客户管理系统之前端页面开发及数据渲染
查看>>
60)模板类去派生新的子类
查看>>
实验三
查看>>