db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From t...@apache.org
Subject cvs commit: db-ojb/lib p6spy.jar
Date Sat, 15 Feb 2003 17:49:27 GMT
thma        2003/02/15 09:49:27

  Modified:    .        build.properties
               src/test/org/apache/ojb spy.properties
               lib      p6spy.jar
  Log:
  integrate P6Spy 1.0
  
  Revision  Changes    Path
  1.31      +1 -1      db-ojb/build.properties
  
  Index: build.properties
  ===================================================================
  RCS file: /home/cvs/db-ojb/build.properties,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- build.properties	9 Feb 2003 16:51:58 -0000	1.30
  +++ build.properties	15 Feb 2003 17:49:25 -0000	1.31
  @@ -26,7 +26,7 @@
   # jakarta-ojb/src/test/org/apache/ojb/spy.properties
   # to tell P6Spy which JDBC driver to use and where to write the log.
   # By default the HSQLDB driver is used.
  -#useP6Spy=true
  +useP6Spy=true
   
   # -------------------------------------------------------------------
   # You should NOT have to edit anything below here.
  
  
  
  1.2       +222 -127  db-ojb/src/test/org/apache/ojb/spy.properties
  
  Index: spy.properties
  ===================================================================
  RCS file: /home/cvs/db-ojb/src/test/org/apache/ojb/spy.properties,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- spy.properties	9 Jul 2002 19:40:25 -0000	1.1
  +++ spy.properties	15 Feb 2003 17:49:26 -0000	1.2
  @@ -1,127 +1,222 @@
  -#################################################################
  -# P6Spy Options File                                            #
  -# See documentation for detailed instructions                   #
  -#################################################################
  -
  -#################################################################
  -# MODULES                                                       #
  -#                                                               #
  -# Modules provide the P6Spy functionality.  If a module, such   #
  -# as module_log is commented out, that functionality will not   #
  -# be available.  If it is not commented out (if it is active),  #
  -# the functionality will be active.                             #
  -#                                                               #
  -# Values set in Modules cannot be reloaded using the            #
  -# reloadproperties variable.  Once they are loaded, they remain #
  -# in memory until the application is restarted.                 #
  -#                                                               #
  -#################################################################
  -
  -module_log=com.p6spy.engine.logging.P6LogSpyDriver
  -#module_outage=com.p6spy.engine.outage.P6OutageSpyDriver
  -
  -#################################################################
  -# REALDRIVER(s)                                                 #
  -#                                                               #
  -# In your application server configuration file you replace the #
  -# "real driver" name with com.p6spy.engine.P6SpyDriver. This is #
  -# where you put the name of your real driver P6Spy can find and #
  -# register your real driver to do the database work.            #
  -#                                                               #
  -# If your application uses several drivers specify them in      #
  -# realdriver2, realdriver3.  See the documentation for more     #
  -# details.                                                      #
  -#                                                               #
  -# Values set in REALDRIVER(s) cannot be reloaded using the      #
  -# reloadproperties variable.  Once they are loaded, they remain #
  -# in memory until the application is restarted.                 #
  -#                                                               #
  -#################################################################
  -
  -# realdriver=org.gjt.mm.mysql.Driver 
  -realdriver=org.hsqldb.jdbcDriver
  -#specifies another driver to use
  -realdriver2=
  -#specifies a third driver to use
  -realdriver3=
  -
  -################################################################
  -# P6LOG SPECIFIC PROPERTIES                                    #
  -################################################################
  -# determines if p6log outputs information
  -trace       = true
  -
  -################################################################
  -# P6OUTAGE 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)
  -#
  -outagedetection=false
  -outagedetectioninterval=
  -
  -
  -################################################################
  -# COMMON PROPERTIES                                            #
  -################################################################
  -
  -# comma separated list of tables to include
  -include     =
  -# comma separated list of tables to exclude
  -exclude     =
  -
  -# sql expression to evaluate if using regex
  -sqlexpression = 
  -
  -# filter what is logged
  -filter=false 
  -
  -# turn on tracing
  -autoflush   = true
  -# name of logfile if trace is on, use "stdout" for standard output.
  -logfile     = spy.log
  -#logfile     = stdout
  -# append to  the p6spy log file.  if this is set to false the
  -# log file is truncated every time.
  -append=true
  -
  -# sets the date format using Java's SimpleDateFormat routine
  -dateformat=
  -
  -#list of categories to explicitly include
  -includecategories=
  -
  -#list of categories to exclude: 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=
  -
  -# 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
  -reloadproperties=false
  -# determines how often should be reloaded in seconds
  -reloadpropertiesinterval=60
  -#if=true then url must be prefixed with p6spy:
  -useprefix=false
  +#################################################################
  +# P6Spy Options File                                            #
  +# See documentation for detailed instructions                   #
  +#################################################################
  +
  +#################################################################
  +# MODULES                                                       #
  +#                                                               #
  +# Modules provide the P6Spy functionality.  If a module, such   #
  +# as module_log is commented out, that functionality will not   #
  +# be available.  If it is not commented out (if it is active),  #
  +# the functionality will be active.                             #
  +#                                                               #
  +# Values set in Modules cannot be reloaded using the            #
  +# reloadproperties variable.  Once they are loaded, they remain #
  +# in memory until the application is restarted.                 #
  +#                                                               #
  +#################################################################
  +
  +module.log=com.p6spy.engine.logging.P6LogFactory
  +#module.outage=com.p6spy.engine.outage.P6OutageFactory
  +
  +#################################################################
  +# REALDRIVER(s)                                                 #
  +#                                                               #
  +# In your application server configuration file you replace the #
  +# "real driver" name with com.p6spy.engine.P6SpyDriver. This is #
  +# where you put the name of your real driver P6Spy can find and #
  +# register your real driver to do the database work.            #
  +#                                                               #
  +# If your application uses several drivers specify them in      #
  +# realdriver2, realdriver3.  See the documentation for more     #
  +# details.                                                      #
  +#                                                               #
  +# Values set in REALDRIVER(s) cannot be reloaded using the      #
  +# reloadproperties variable.  Once they are loaded, they remain #
  +# in memory until the application is restarted.                 #
  +#                                                               #
  +#################################################################
  +
  +# oracle driver
  +# realdriver=oracle.jdbc.driver.OracleDriver
  +
  +# mysql Connector/J driver
  +# realdriver=com.mysql.jdbc.Driver
  +
  +# informix driver
  +# realdriver=com.informix.jdbc.IfxDriver
  +
  +# ibm db2 driver
  +# realdriver=COM.ibm.db2.jdbc.net.DB2Driver
  +
  +# the mysql open source driver
  +#realdriver=org.gjt.mm.mysql.Driver
  +
  +# the hsqldb jdbc driver (OJB testsuite and tutorials)
  +realdriver=org.hsqldb.jdbcDriver
  +
  +#specifies another driver to use
  +realdriver2=
  +#specifies a third driver to use
  +realdriver3=
  +
  +################################################################
  +# P6LOG SPECIFIC PROPERTIES                                    #
  +################################################################
  +# no properties currently available
  +
  +################################################################
  +# P6OUTAGE 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)
  +#
  +outagedetection=false
  +outagedetectioninterval=
  +
  +################################################################
  +# COMMON PROPERTIES                                            #
  +################################################################
  +
  +# comma separated list of tables to include
  +include     =
  +# comma separated list of tables to exclude
  +exclude     =
  +
  +# sql expression to evaluate if using regex
  +sqlexpression = 
  +
  +# filter what is logged
  +filter=false 
  +
  +# turn on tracing
  +autoflush   = true
  +
  +# 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=
  +
  +# 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
  +reloadproperties=false
  +# 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
  +
  +# 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
  +
  +# append to  the p6spy log file.  if this is set to false the
  +# 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
  +
  +
  +#################################################################
  +# DataSource replacement                                        #
  +#                                                               #
  +# Replace the real DataSource class in your application server  #
  +# configuration with the name com.p6spy.engine.spy.P6DataSource,#
  +# 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;ibmhost,databaseName;mydb
  +
  +
  +#################################################################
  +# 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).                              #
  +#                                                               #
  +#################################################################
  +#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
  
  
  
  1.2       +357 -362  db-ojb/lib/p6spy.jar
  
  	<<Binary file>>
  
  

Mime
View raw message