[Db-derby Wiki] Update of "UndocumentedDerbyBehavior" by KatheyMarsden

[Apache Wiki <wi...@apache.org>]

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:
http://wiki.apache.org/db-derby/UndocumentedDerbyBehavior

------------------------------------------------------------------------------
  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.  
+ 

Re: [Db-derby Wiki] Update of "UndocumentedDerbyBehavior" by KatheyMarsden

[Kathey Marsden <km...@sbcglobal.net>]

Myrna van Lunteren wrote:
> Is there a reason why this is/can not get documented in the manuals?
>
I am only speculating as I was not involved in the original change, but 
I wonder if it is because System properties are not the ideal solution 
because they cannot be separated when being used across ClassLoaders.  
Previously derby.system.home was the only system property  we really had 
to worry about.  Adding new system properties potentially complicates 
the issue further.  See DERBY-1228 for concerns about 
derby.system.home.  So I am guessing there was concern over creating a 
public interface that introduced more system properties.

Kathey

Re: [Db-derby Wiki] Update of "UndocumentedDerbyBehavior" by KatheyMarsden

[Myrna van Lunteren <m....@gmail.com>]

Is there a reason why this is/can not get documented in the manuals?

Thx,
Myrna