[DERBY-5553] System property for client tracing -Dderby.client.traceDirectory does not work with XADataSource

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.2.2, 10.9.1.0
• Fix Version/s: 10.10.2.0, 10.11.1.1
• Component/s: Network Client
• Labels: derby_backport_reject_10_9 derby_triage10_11
• Urgency: Normal
• Issue & fix info: High Value Fix, Newcomer, Patch Available
• Assignee: Katherine Marsden
• Reporter: Katherine Marsden
• Created: 23/Dec/11 00:59
• Updated: 21/Jan/15 00:23
• Resolved: 04/Sep/13 19:20

Description

The client system property -Dderby.client.traceDirectory does not work with ClientXADataSource. No trace files are created if this property is set when making XA Connections.

I am sure it works fine with DriverManager connections and also checked tracing works fine using connection attributes and XA with. ds.setConnectionAttributes("traceDirectory=./traceDir");

I have not checked ClientDataSource or ClientConnectionPoolDataSource.

Attached is a reproduction for this issue.
mkdir ./traceDir

javac -g XATemplate.java utilXid.java
java -Dderby.client.traceDirectory="./traceDir" XATemplate

You will see that traceDir is empty.
This came up when debugging DERBY-5552

Issue Links

• is related to: DERBY-5552 Derby threads hanging when using ClientXADataSource and a deadlock or lock timeout occurs