db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DebugPropertiesTmpl" by StanleyBradbury
Date Mon, 14 Aug 2006 14:00:40 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by StanleyBradbury:
http://wiki.apache.org/db-derby/DebugPropertiesTmpl

New page:
## Added 2006-08-13
== Annotated derby.properties useful for development and test environments   ==
The following derby.properties file contains properties I find useful when debugging a system
using derby.  Many of the properties are commented out and should only to enabled when needed
to address specific problems (unless you don't care about the additional processing and disk
space overhead).  The lines where derby properties are commented out start with the string
{{{#.. derby.}}}. Refer to the Derby manuals for a more complete description of each property.

{{{
######################################################################
#            Example DEBUG derby.properties file 
## Create the derby.properties file in the derby.system.home folder.  
## By default the derby.log file is written to derby.system.home.  If you are unsure
##  where to place the properties use the folder containing the derby.log file.
##  Uncomment properties preceeded by the string '#.. ' to make them active.
###################################################
## The next three properties can be set for all test situations.  They have a 
## very slight performance impact but insure we get all messages 
##  and that the log is not automatically removed.
#  -- Append to the log file rather than overwriting it - manually remove 
#  -- the derby.log when it becomes large
derby.infolog.append=true
#  -- Log all errors/messages of any severity (will list deadlocks)
derby.stream.error.logSeverityLevel=0
#  -- Log all Network Server connections (if any)
derby.drda.logConnections=true
##################################################
##   When you need to trace what requests (SQL) the application(s) is/are 
##     making of Cloudscape set the following property (Uncomment the line).
## !! CAUTION !! : You will need to manage the size of the derby.log file 
##  !!   - it can grow to 100's of MBs or larger !!
# -- Log all SQL received
#.. derby.language.logStatementText=true
###################################################
## Performance problems: 
# --  write query plan to log
#.. derby.language.logQueryPlan=true
###################################################
## If you are encountering locking / concurrency problems set (uncomment) the
##  following two properties
#  -- Log all deadlocks 
#.. derby.locks.monitor=true
# -- Writes a stack trace of all threads involved in lock problems 
# --    (not just the victims) to the log
#.. derby.locks.deadlockTrace=true
####################################################
##  These properties adjust the time a process will wait for a lock and 
##    how often Cloudscape checks for deadlocks.
# -- Hold locks for five minutes before timeout
#.. derby.locks.waitTimeout=300
# -- If deadlocks are occurring lengthen wait 
# --      (waitTimeout must be < deadlockTimeout)
#.. derby.locks.deadlockTimeout=310
#       END of Example properties file
}}}

Mime
View raw message