EOS下控制台以及图形界面打印sql语句

场景需求：在eos中打印sql语句，包括数据实体，查询实体和命名sql的sql语句。

所需资源：

P6spy：负责拦截sql，并打印。
Sqlprofiler：解析p6spy拦截的sql，在基于swing的图形界面上显示，并提供监控分析功能。
Spy.properties：p6spy配置文件，用来指定数据库驱动，打印sql的目的地（文件，控制台，sqlprofiler界面），打印格式等。

EOS控制台打印

  1. 复制p6spy.ar,sqlprofiler.jar到web应用的lib目录下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
  2. 复制spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
  3. 修改系统配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改数据源的驱动路径为：com.p6spy.engine.spy.P6SpyDriver。
  4. 修改spy.properties文件为如下：

################################################################P6Spy Options File #

  1. See documentation for detailed instructions #
    #################################################################

    #################################################################
  2. MODULES #
  3. #
  4. Modules provide the P6Spy functionality. If a module, such #
  5. as module_log is commented out, that functionality will not #
  6. be available. If it is not commented out (if it is active), #
  7. the functionality will be active. #
  8. #
  9. Values set in Modules cannot be reloaded using the #
  10. reloadproperties variable. Once they are loaded, they remain #
  11. in memory until the application is restarted. #
  12. #
    #################################################################

    module.log=com.p6spy.engine.logging.P6LogFactory
    #module.outage=com.p6spy.engine.outage.P6OutageFactory

    #################################################################
  13. REALDRIVER(s) #
  14. #
  15. In your application server configuration file you replace the #
  16. "real driver" name with com.p6spy.engine.P6SpyDriver. This is #
  17. where you put the name of your real driver P6Spy can find and #
  18. register your real driver to do the database work. #
  19. #
  20. If your application uses several drivers specify them in #
  21. realdriver2, realdriver3. See the documentation for more #
  22. details. #
  23. #
  24. Values set in REALDRIVER(s) cannot be reloaded using the #
  25. reloadproperties variable. Once they are loaded, they remain #
  26. in memory until the application is restarted. #
  27. #
    #################################################################
  28. oracle driver
  29. realdriver=oracle.jdbc.driver.OracleDriver
  30. mysql Connector/J driver
  31. realdriver=com.mysql.jdbc.Driver
  32. informix driver
  33. realdriver=com.informix.jdbc.IfxDriver
  34. ibm db2 driver
  35. realdriver=COM.ibm.db2.jdbc.net.DB2Driver
  36. the mysql open source driver
    realdriver=com.mysql.jdbc.Driver

    #specifies another driver to use
    realdriver2=
    #specifies a third driver to use
    realdriver3=



    #the DriverManager class sequentially tries every driver that is
    #registered to find the right driver. In some instances, it's possible to
    #load up the realdriver before the p6spy driver, in which case your connections
    #will not get wrapped as the realdriver will "steal" the connection before
    #p6spy sees it. Set the following property to "true" to cause p6spy to
    #explicitily deregister the realdrivers
    deregisterdrivers=false

    ################################################################
  37. P6LOG SPECIFIC PROPERTIES #
    ################################################################
  38. no properties currently available

    ################################################################
  39. EXECUTION THRESHOLD PROPERTIES #
    ################################################################
  40. This feature applies to the standard logging of P6Spy. #
  41. While the standard logging logs out every statement #
  42. regardless of its execution time, this feature puts a time #
  43. condition on that logging. Only statements that have taken #
  44. longer than the time specified (in milliseconds) will be #
  45. logged. This way it is possible to see only statements that #
  46. have exceeded some high water mark. #
  47. This time is reloadable. #
    #
  48. executionthreshold=integer time (milliseconds)
    #
    executionthreshold=

    ################################################################
  49. P6OUTAGE SPECIFIC PROPERTIES #
    ################################################################
  50. Outage Detection
    #
  51. This feature detects long-running statements that may be indicative of
  52. a database outage problem. If this feature is turned on, it will log any
  53. statement that surpasses the configurable time boundary during its execution.
  54. When this feature is enabled, no other statements are logged except the long
  55. running statements. The interval property is the boundary time set in seconds.
  56. For example, if this is set to 2, then any statement requiring at least 2
  57. seconds will be logged. Note that the same statement will continue to be logged
  58. for as long as it executes. So if the interval is set to 2, and the query takes
  59. 11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
    #
  60. outagedetection=true|false
  61. outagedetectioninterval=integer time (seconds)
    #
    outagedetection=false
    outagedetectioninterval=

    ################################################################
  62. COMMON PROPERTIES #
    ################################################################
  63. filter what is logged
    filter=false
  64. comma separated list of tables to include when filtering
    include =
  65. comma separated list of tables to exclude when filtering
    exclude =
  66. sql expression to evaluate if using regex filtering
    sqlexpression =


  67. turn on tracing
    autoflush = true
  68. sets the date format using Java's SimpleDateFormat routine
    dateformat=yyyy-MM-dd HH:mm:ss:SS

    #list of categories to explicitly include
    includecategories=

    #list of categories to exclude: error, info, batch, debug, statement,
    #commit, rollback and result are valid values
    excludecategories=info,debug,result,batch



    #allows you to use a regex engine or your own matching engine to determine
    #which statements to log
    #
    #stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
    #stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
    stringmatcher=
  69. prints a stack trace for every statement logged
    stacktrace=false
  70. if stacktrace=true, specifies the stack trace to print
    stacktraceclass=
  71. determines if property file should be reloaded
    reloadproperties=false
  72. determines how often should be reloaded in seconds
    reloadpropertiesinterval=60

    #if=true then url must be prefixed with p6spy:
    useprefix=false

    #specifies the appender to use for logging
    #appender=com.p6spy.engine.logging.appender.Log4jLogger
    appender=com.p6spy.engine.logging.appender.StdoutLogger
    #appender=com.p6spy.engine.logging.appender.FileLogger
  73. name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
    logfile = spy.log
  74. append to the p6spy log file. if this is set to false the
  75. log file is truncated every time. (file logger only)
    append=true

    #The following are for log4j logging only
    log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
    log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
    log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n

    #log4j.appender.SQLPROFILER_CLIENT=org.apache.log4j.net.SocketAppender
    #log4j.appender.SQLPROFILER_CLIENT.RemoteHost=localhost
    #log4j.appender.SQLPROFILER_CLIENT.Port=4445
    #log4j.appender.SQLPROFILER_CLIENT.LocationInfo=true

    log4j.logger.p6spy=INFO,STDOUT



    #################################################################
  76. DataSource replacement #
  77. #
  78. Replace the real DataSource class in your application server #
  79. configuration with the name com.p6spy.engine.spy.P6DataSource,#
  80. then add the JNDI name and class name of the real #
  81. DataSource here #
  82. #
  83. Values set in this item cannot be reloaded using the #
  84. reloadproperties variable. Once it is loaded, it remains #
  85. in memory until the application is restarted. #
  86. #
    #################################################################
    #realdatasource=/RealMySqlDS
    #realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource

    #################################################################
  87. DataSource properties #
  88. #
  89. If you are using the DataSource support to intercept calls #
  90. to a DataSource that requires properties for proper setup, #
  91. define those properties here. Use name value pairs, separate #
  92. the name and value with a semicolon, and separate the #
  93. pairs with commas. #
  94. #
  95. The example shown here is for mysql #
  96. #
    #################################################################
    #realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb



    #################################################################
  97. JNDI DataSource lookup #
  98. #
  99. If you are using the DataSource support outside of an app #
  100. server, you will probably need to define the JNDI Context #
  101. environment. #
  102. #
  103. If the P6Spy code will be executing inside an app server then #
  104. do not use these properties, and the DataSource lookup will #
  105. use the naming context defined by the app server. #
  106. #
  107. The two standard elements of the naming environment are#
  108. jndicontextfactory and jndicontextproviderurl. If you need #
  109. additional elements, use the jndicontextcustom property. #
  110. You can define multiple properties in jndicontextcustom, #
  111. in name value pairs. Separate the name and value with a #
  112. semicolon, and separate the pairs with commas. #
  113. #
  114. The example shown here is for a standalone program running on #
  115. a machine that is also running JBoss, so the JDNI context #
  116. is configured for JBoss (3.0.4). #
  117. #
    #################################################################
    #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
  118. 启动eos服务器，控制台在调用数据库查询的时候会打印如下的内容，即配置成功：

文件中打印

  1. 复制p6spy.ar,sqlprofiler.jar到web应用的lib目录下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
  2. 复制spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
  3. 修改系统配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改数据源的驱动路径为：com.p6spy.engine.spy.P6SpyDriver。
  4. 修改spy.properties文件为如下：

#################################################################

  1. P6Spy Options File #
  2. See documentation for detailed instructions #
    #################################################################

    #################################################################
  3. MODULES #
  4. #
  5. Modules provide the P6Spy functionality. If a module, such #
  6. as module_log is commented out, that functionality will not #
  7. be available. If it is not commented out (if it is active), #
  8. the functionality will be active. #
  9. #
  10. Values set in Modules cannot be reloaded using the #
  11. reloadproperties variable. Once they are loaded, they remain #
  12. in memory until the application is restarted. #
  13. #
    #################################################################

    module.log=com.p6spy.engine.logging.P6LogFactory
    #module.outage=com.p6spy.engine.outage.P6OutageFactory

    #################################################################
  14. REALDRIVER(s) #
  15. #
  16. In your application server configuration file you replace the #
  17. "real driver" name with com.p6spy.engine.P6SpyDriver. This is #
  18. where you put the name of your real driver P6Spy can find and #
  19. register your real driver to do the database work. #
  20. #
  21. If your application uses several drivers specify them in #
  22. realdriver2, realdriver3. See the documentation for more #
  23. details. #
  24. #
  25. Values set in REALDRIVER(s) cannot be reloaded using the #
  26. reloadproperties variable. Once they are loaded, they remain #
  27. in memory until the application is restarted. #
  28. #
    #################################################################
  29. oracle driver
  30. realdriver=oracle.jdbc.driver.OracleDriver
  31. mysql Connector/J driver
  32. realdriver=com.mysql.jdbc.Driver
  33. informix driver
  34. realdriver=com.informix.jdbc.IfxDriver
  35. ibm db2 driver
  36. realdriver=COM.ibm.db2.jdbc.net.DB2Driver
  37. the mysql open source driver
    realdriver=com.mysql.jdbc.Driver

    #specifies another driver to use
    realdriver2=
    #specifies a third driver to use
    realdriver3=



    #the DriverManager class sequentially tries every driver that is
    #registered to find the right driver. In some instances, it's possible to
    #load up the realdriver before the p6spy driver, in which case your connections
    #will not get wrapped as the realdriver will "steal" the connection before
    #p6spy sees it. Set the following property to "true" to cause p6spy to
    #explicitily deregister the realdrivers
    deregisterdrivers=false

    ################################################################
  38. P6LOG SPECIFIC PROPERTIES #
    ################################################################
  39. no properties currently available

    ################################################################
  40. EXECUTION THRESHOLD PROPERTIES #
    ################################################################
  41. This feature applies to the standard logging of P6Spy. #
  42. While the standard logging logs out every statement #
  43. regardless of its execution time, this feature puts a time #
  44. condition on that logging. Only statements that have taken #
  45. longer than the time specified (in milliseconds) will be #
  46. logged. This way it is possible to see only statements that #
  47. have exceeded some high water mark. #
  48. This time is reloadable. #
    #
  49. executionthreshold=integer time (milliseconds)
    #
    executionthreshold=

    ################################################################
  50. P6OUTAGE SPECIFIC PROPERTIES #
    ################################################################
  51. Outage Detection
    #
  52. This feature detects long-running statements that may be indicative of
  53. a database outage problem. If this feature is turned on, it will log any
  54. statement that surpasses the configurable time boundary during its execution.
  55. When this feature is enabled, no other statements are logged except the long
  56. running statements. The interval property is the boundary time set in seconds.
  57. For example, if this is set to 2, then any statement requiring at least 2
  58. seconds will be logged. Note that the same statement will continue to be logged
  59. for as long as it executes. So if the interval is set to 2, and the query takes
  60. 11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
    #
  61. outagedetection=true|false
  62. outagedetectioninterval=integer time (seconds)
    #
    outagedetection=false
    outagedetectioninterval=

    ################################################################
  63. COMMON PROPERTIES #
    ################################################################
  64. filter what is logged
    filter=false
  65. comma separated list of tables to include when filtering
    include =
  66. comma separated list of tables to exclude when filtering
    exclude =
  67. sql expression to evaluate if using regex filtering
    sqlexpression =
  68. turn on tracing
    autoflush = true
  69. sets the date format using Java's SimpleDateFormat routine
    dateformat=yyyy-MM-dd HH:mm:ss:SS

    #list of categories to explicitly include
    includecategories=

    #list of categories to exclude: error, info, batch, debug, statement,
    #commit, rollback and result are valid values
    excludecategories=info,debug,result,batch



    #allows you to use a regex engine or your own matching engine to determine
    #which statements to log
    #
    #stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
    #stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
    stringmatcher=
  70. prints a stack trace for every statement logged
    stacktrace=false
  71. if stacktrace=true, specifies the stack trace to print
    stacktraceclass=
  72. determines if property file should be reloaded
    reloadproperties=false
  73. determines how often should be reloaded in seconds
    reloadpropertiesinterval=60

    #if=true then url must be prefixed with p6spy:
    useprefix=false

    #specifies the appender to use for logging
    #appender=com.p6spy.engine.logging.appender.Log4jLogger
    #appender=com.p6spy.engine.logging.appender.StdoutLogger
    appender=com.p6spy.engine.logging.appender.FileLogger
  74. name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
    logfile = c:/abc/spy.log
  75. append to the p6spy log file. if this is set to false the
  76. log file is truncated every time. (file logger only)
    append=true

    #The following are for log4j logging only
    #log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
    #log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
    #log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n

    #log4j.appender.CHAINSAW_CLIENT=org.apache.log4j.net.SocketAppender
    #log4j.appender.CHAINSAW_CLIENT.RemoteHost=localhost
    #log4j.appender.CHAINSAW_CLIENT.Port=4445
    #log4j.appender.CHAINSAW_CLIENT.LocationInfo=true

    log4j.logger.p6spy=INFO,STDOUT



    #################################################################
  77. DataSource replacement #
  78. #
  79. Replace the real DataSource class in your application server #
  80. configuration with the name com.p6spy.engine.spy.P6DataSource,#
  81. then add the JNDI name and class name of the real #
  82. DataSource here #
  83. #
  84. Values set in this item cannot be reloaded using the #
  85. reloadproperties variable. Once it is loaded, it remains #
  86. in memory until the application is restarted. #
  87. #
    #################################################################
    #realdatasource=/RealMySqlDS
    #realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource

    #################################################################
  88. DataSource properties #
  89. #
  90. If you are using the DataSource support to intercept calls #
  91. to a DataSource that requires properties for proper setup, #
  92. define those properties here. Use name value pairs, separate #
  93. the name and value with a semicolon, and separate the #
  94. pairs with commas. #
  95. #
  96. The example shown here is for mysql #
  97. #
    #################################################################
    #realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb



    #################################################################
  98. JNDI DataSource lookup #
  99. #
  100. If you are using the DataSource support outside of an app #
  101. server, you will probably need to define the JNDI Context #
  102. environment. #
  103. #
  104. If the P6Spy code will be executing inside an app server then #
  105. do not use these properties, and the DataSource lookup will #
  106. use the naming context defined by the app server. #
  107. #
  108. The two standard elements of the naming environment are#
  109. jndicontextfactory and jndicontextproviderurl. If you need #
  110. additional elements, use the jndicontextcustom property. #
  111. You can define multiple properties in jndicontextcustom, #
  112. in name value pairs. Separate the name and value with a #
  113. semicolon, and separate the pairs with commas. #
  114. #
  115. The example shown here is for a standalone program running on #
  116. a machine that is also running JBoss, so the JDNI context #
  117. is configured for JBoss (3.0.4). #
  118. #
    #################################################################
    #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
  119. 启动前请在指定的路径下新建日志文件（logfile = c:/abc/spy.log），启动EOS服务器会在c:/abc/spy.log看到如下内容，表示配置成功：

图形界面中打印

  1. 复制p6spy.ar,sqlprofiler.jar到web应用的lib目录下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
  2. 复制spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
  3. 修改系统配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改数据源的驱动路径为：com.p6spy.engine.spy.P6SpyDriver。
  4. 修改spy.properties文件为如下：

#################################################################

  1. P6Spy Options File #
  2. See documentation for detailed instructions #
    #################################################################

    #################################################################
  3. MODULES #
  4. #
  5. Modules provide the P6Spy functionality. If a module, such #
  6. as module_log is commented out, that functionality will not #
  7. be available. If it is not commented out (if it is active), #
  8. the functionality will be active. #
  9. #
  10. Values set in Modules cannot be reloaded using the #
  11. reloadproperties variable. Once they are loaded, they remain #
  12. in memory until the application is restarted. #
  13. #
    #################################################################

    module.log=com.p6spy.engine.logging.P6LogFactory
    #module.outage=com.p6spy.engine.outage.P6OutageFactory

    #################################################################
  14. REALDRIVER(s) #
  15. #
  16. In your application server configuration file you replace the #
  17. "real driver" name with com.p6spy.engine.P6SpyDriver. This is #
  18. where you put the name of your real driver P6Spy can find and #
  19. register your real driver to do the database work. #
  20. #
  21. If your application uses several drivers specify them in #
  22. realdriver2, realdriver3. See the documentation for more #
  23. details. #
  24. #
  25. Values set in REALDRIVER(s) cannot be reloaded using the #
  26. reloadproperties variable. Once they are loaded, they remain #
  27. in memory until the application is restarted. #
  28. #
    #################################################################
  29. oracle driver
  30. realdriver=oracle.jdbc.driver.OracleDriver
  31. mysql Connector/J driver
  32. realdriver=com.mysql.jdbc.Driver
  33. informix driver
  34. realdriver=com.informix.jdbc.IfxDriver
  35. ibm db2 driver
  36. realdriver=COM.ibm.db2.jdbc.net.DB2Driver
  37. the mysql open source driver
    realdriver=com.mysql.jdbc.Driver

    #specifies another driver to use
    realdriver2=
    #specifies a third driver to use
    realdriver3=



    #the DriverManager class sequentially tries every driver that is
    #registered to find the right driver. In some instances, it's possible to
    #load up the realdriver before the p6spy driver, in which case your connections
    #will not get wrapped as the realdriver will "steal" the connection before
    #p6spy sees it. Set the following property to "true" to cause p6spy to
    #explicitily deregister the realdrivers
    deregisterdrivers=false

    ################################################################
  38. P6LOG SPECIFIC PROPERTIES #
    ################################################################
  39. no properties currently available

    ################################################################
  40. EXECUTION THRESHOLD PROPERTIES #
    ################################################################
  41. This feature applies to the standard logging of P6Spy. #
  42. While the standard logging logs out every statement #
  43. regardless of its execution time, this feature puts a time #
  44. condition on that logging. Only statements that have taken #
  45. longer than the time specified (in milliseconds) will be #
  46. logged. This way it is possible to see only statements that #
  47. have exceeded some high water mark. #
  48. This time is reloadable. #
    #
  49. executionthreshold=integer time (milliseconds)
    #
    executionthreshold=

    ################################################################
  50. P6OUTAGE SPECIFIC PROPERTIES #
    ################################################################
  51. Outage Detection
    #
  52. This feature detects long-running statements that may be indicative of
  53. a database outage problem. If this feature is turned on, it will log any
  54. statement that surpasses the configurable time boundary during its execution.
  55. When this feature is enabled, no other statements are logged except the long
  56. running statements. The interval property is the boundary time set in seconds.
  57. For example, if this is set to 2, then any statement requiring at least 2
  58. seconds will be logged. Note that the same statement will continue to be logged
  59. for as long as it executes. So if the interval is set to 2, and the query takes
  60. 11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
    #
  61. outagedetection=true|false
  62. outagedetectioninterval=integer time (seconds)
    #
    outagedetection=false
    outagedetectioninterval=

    ################################################################
  63. COMMON PROPERTIES #
    ################################################################
  64. filter what is logged
    filter=false
  65. comma separated list of tables to include when filtering
    include =
  66. comma separated list of tables to exclude when filtering
    exclude =
  67. sql expression to evaluate if using regex filtering
    sqlexpression =
  68. turn on tracing
    autoflush = true
  69. sets the date format using Java's SimpleDateFormat routine
    dateformat=

    #list of categories to explicitly include
    includecategories=

    #list of categories to exclude: error, info, batch, debug, statement,
    #commit, rollback and result are valid values
    excludecategories=info,debug,result,batch



    #allows you to use a regex engine or your own matching engine to determine
    #which statements to log
    #
    #stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
    #stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
    stringmatcher=
  70. prints a stack trace for every statement logged
    stacktrace=false
  71. if stacktrace=true, specifies the stack trace to print
    stacktraceclass=
  72. determines if property file should be reloaded
    reloadproperties=false
  73. determines how often should be reloaded in seconds
    reloadpropertiesinterval=60

    #if=true then url must be prefixed with p6spy:
    useprefix=false

    #specifies the appender to use for logging
    appender=com.p6spy.engine.logging.appender.Log4jLogger
    #appender=com.p6spy.engine.logging.appender.StdoutLogger
    #appender=com.p6spy.engine.logging.appender.FileLogger
  74. name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
    #logfile = spy.log
  75. append to the p6spy log file. if this is set to false the
  76. log file is truncated every time. (file logger only)
    append=true

    #The following are for log4j logging only
    #log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
    #log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
    #log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n

    log4j.appender.SQLPROFILER_CLIENT=org.apache.log4j.net.SocketAppender
    log4j.appender.SQLPROFILER_CLIENT.RemoteHost=localhost
    log4j.appender.SQLPROFILER_CLIENT.Port=4445
    log4j.appender.SQLPROFILER_CLIENT.LocationInfo=true

    #log4j.logger.p6spy=INFO,STDOUT
    log4j.logger.p6spy=DEBUG, SQLPROFILER_CLIENT



    #################################################################
  77. DataSource replacement #
  78. #
  79. Replace the real DataSource class in your application server #
  80. configuration with the name com.p6spy.engine.spy.P6DataSource,#
  81. then add the JNDI name and class name of the real #
  82. DataSource here #
  83. #
  84. Values set in this item cannot be reloaded using the #
  85. reloadproperties variable. Once it is loaded, it remains #
  86. in memory until the application is restarted. #
  87. #
    #################################################################
    #realdatasource=/RealMySqlDS
    #realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource

    #################################################################
  88. DataSource properties #
  89. #
  90. If you are using the DataSource support to intercept calls #
  91. to a DataSource that requires properties for proper setup, #
  92. define those properties here. Use name value pairs, separate #
  93. the name and value with a semicolon, and separate the #
  94. pairs with commas. #
  95. #
  96. The example shown here is for mysql #
  97. #
    #################################################################
    #realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb



    #################################################################
  98. JNDI DataSource lookup #
  99. #
  100. If you are using the DataSource support outside of an app #
  101. server, you will probably need to define the JNDI Context #
  102. environment. #
  103. #
  104. If the P6Spy code will be executing inside an app server then #
  105. do not use these properties, and the DataSource lookup will #
  106. use the naming context defined by the app server. #
  107. #
  108. The two standard elements of the naming environment are#
  109. jndicontextfactory and jndicontextproviderurl. If you need #
  110. additional elements, use the jndicontextcustom property. #
  111. You can define multiple properties in jndicontextcustom, #
  112. in name value pairs. Separate the name and value with a #
  113. semicolon, and separate the pairs with commas. #
  114. #
  115. The example shown here is for a standalone program running on #
  116. a machine that is also running JBoss, so the JDNI context #
  117. is configured for JBoss (3.0.4). #
  118. #
    #################################################################
    #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
  119. 打开命令行窗口，进入sqlprofiler所在的路径，我这里是：D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib，执行

java -jar sqlprofiler.jar命令，弹出如下窗口：

启动EOS服务器，调用数据库查询功能，sqlprofiler中会显示类似于如下的信息：

配置完成。

<__________________________本文系转载，特此声明——————————————>

所需资源：

转载于:https://www.cnblogs.com/JOEH60/p/8706319.html

EOS下控制台以及图形界面打印sql语句相关推荐

  1. Ubuntu18.04下无法进入图形界面、无法调整分辨率、无法重装显卡驱动问题的解决方式

    Ubuntu18.04下无法进入图形界面.无法调整分辨率.无法重装显卡驱动问题的解决方式 参考文章: (1)Ubuntu18.04下无法进入图形界面.无法调整分辨率.无法重装显卡驱动问题的解决方式 ( ...

  2. CentOS7下安装GUI图形界面

    1.如何在centOS7下安装GUI图形界面 当你安装centOS7服务器版本的时候,系统默认是不会安装GUI的图形界面程序,这个需要手动安装CentOS7 Gnome GUI包. 2.在系统下使用命 ...

  3. 如何打开电脑c语言窗口,C语言控制台窗口图形界面编程（五）. -电脑资料

    控制文本的移动是控制台窗口界面编程的一个很重要的功能,有了这个功能我们可以实现界面的滚动, BOOL ScrollConsoleScreenBuffer(      //文本移动函数 HANDLE h ...

  4. Mybatis 开启控制台打印sql语句

    概述 springboot+mybatis整合过程中,开启控制台sql语句打印的多种方式: 方法1 在springboot+mybatis整合中,可以将springboot的配置文件添加如下一段也可: ...

  5. mybatis开启log_mybatis使用spring-druid数据源连接池配置log4j打印sql语句以及开启监控平台...

    杂七杂的杂 作为程序员,开发工程中,一套利于测试或者监控的工具很重要,mybatis默认没有提供log4j的打印sql语句的配置. 这对于开发rest服务,提供接口的开发者而言,是在很不好做,再加上m ...

  6. php打印mysql sql_php的打印sql语句的方法

    echo M()->_sql(); 这样就可以调试当前生成的sql语句: //获取指定天的开始时间和结束时间 $datez="2016-05-12"; $t = strtot ...

  7. Spring boot mybatis 打印SQL语句

    有时候从前端传参数到后端查数据库的时候不是很清楚的知道哪些参数能起作用,这个时候就需要简便的sql语句让你知道数据查询的过程中的参数,SQL语句了. 第一种方式,用mybatis集成的方式,在你的ap ...

  8. windows下bat处理执行Mysql的sql语句

    这篇文章主要介绍了windows下bat批处理执行Mysql的sql语句,需要的朋友可以参考下 有时候我们需要用bat来定时执行mysql那么就可以参考下面的代码 直接上代码: @ECHO OFF S ...

  9. Mysql实现文章查询上一篇和下一篇功能，附sql语句?

    mysql实现文章查询上一篇和下一篇功能,附sql语句? 最近在做一个项目用到的文章查询上一篇和下一篇功能,详见:http://www.yifen5.com Mysql实现文章查询上一篇和下一篇功能, ...

最新文章

  1. Cracking the coding interview--Q2.2
  2. VS2010在工具栏上创建查找组合框，即：CMFCToolBar中加入CMFCToolBarComboBoxButton
  3. 分层级联Transformer！苏黎世联邦提出TransCNN: 显著降低了计算/空间复杂度！
  4. FirstDay@JavaOne2017
  5. 【机器学习】理解机器学习
  6. DAG的深度优先搜索标记
  7. .sh是什么语言_为什么《山海经·中次二经》中，把“西王母”叫做“马腹”？...
  8. Axure高保真智慧校园管理系统/校园管理/人事管理/学籍管理/教学管理/流程审批/备课管理/考务管理/成绩管理/排课管理/选课管理/选课系统/调课申请/教师考评管理/web端管理系统
  9. 《jBPM4工作流应用开发指南》这本书
  10. 181113每日一句
  11. python3.5------用户的三次验证
  12. 小凡模拟器（DynamipsGUI）打不开的简单解决方法
  13. SEO优化与网站浏览量提升
  14. Python实现最近邻nearest、双线性bilinear、双三次bicubic插值
  15. 入职阿里两年的工作总结
  16. 【MySQL学习】数据库问题及着重点汇总
  17. 清华计算机考研报考人数,2020部分院校考研报考人数统计
  18. VPS云主机怎么用？
  19. 问卷星破除输入框粘贴限制的两种方法
  20. 可控硅整流电路中的波形系数

热门文章

  1. GSM手机SMS编码解码
  2. Java™ 教程（字符流）
  3. 取代现有电商和实体店菜市场的新模式
  4. Rancher通过Aliyun-slb服务对接阿里云SLB教程
  5. 如何正确使用SqlConnection
  6. Css实现的鼠标滑动选项卡菜单代码
  7. linux文件目录类常用命令
  8. SqlServer中获取所有数据库，所有表，所有字段
  9. python3 进程
  10. MIT自然语言处理第三讲：概率语言模型