[DERBY-1275] Provide a way to enable client tracing without changing the application

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.3.1.4
• Component/s: Network Client
• Urgency: Normal
• Assignee: Mamta A. Satoor
• Reporter: Katherine Marsden
• Created: 02/May/06 11:27
• Updated: 06/Jul/07 15:55
• Resolved: 06/Feb/07 22:06

Description

Currently the client tracing can be enabled by setting attributes on the client url, setXXX methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be enabled in a deployed client application because all of these API's require modification of the application or its configuration files.

It would be good to have a global way to turn on client tracing. A system property pointing to a property file is one possibility but probably not ideal because of the impact in class loader contexts. I am not sure what the other possiblities are,

Issue Links

• relates to: DERBY-2754 Client connections should not fail if permission is not granted to read derby.client.traceLevel and derby.client.traceDirectory