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 "UndocumentedDerbyBehavior" by KatheyMarsden
Date Thu, 07 Jun 2007 17:53:46 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 KatheyMarsden:

  Currently, the client tracing can be enabled by setting jdbc url attributes or through setXXX
methods on the DataSource or by calling DriverManager.setLogWriter method (More information
on these options can be found in the Server and Administration Guide). All these options require
changing the client code which may not be a feasible option for a deployed client application.
To get around this, in Derby 10.3, 2 new JVM properties([http://issues.apache.org/jira/browse/DERBY-1275
DERBY-1275]) have been added. They are namely, derby.client.traceLevel and derby.client.traceDirectory.
When the client application is started, the users can include these 2 JVM properties to start
the client side tracing. eg
  java -Dderby.client.traceDirectory=./traceDir -Dderby.client.traceLevel=64 clientApplication
+ When running under security manager, read permission for these properties is required. 
If permission to read the properties is not allowed, the properties will be ignored and tracing
will not be affected.  

View raw message