[
https://issues.apache.org/jira/browse/DERBY-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-5553:
----------------------------------
Attachment: derby-5553_codediff.txt
Here is a patch for the code changes for this issue. DataSources were looking
only at the attributes and not system properties. I tested the change with the
reproduction and also with ConnectionPoolDataSource. I will look at writing
tests. I don't think we have existing tests for testing the tracing system
properties.
> System property for client tracing -Dderby.client.traceDirectory does not
> work with XADataSource
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-5553
> URL: https://issues.apache.org/jira/browse/DERBY-5553
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.8.2.2, 10.9.1.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Labels: derby_triage10_11
> Attachments: derby-5553_codediff.txt, utilXid.java, XATemplate.java
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
