You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org> on 2012/02/17 19:32:00 UTC
[jira] [Updated] (DERBY-5553) System property for client tracing
-Dderby.client.traceDirectory does not work with XADataSource
[ https://issues.apache.org/jira/browse/DERBY-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5553:
----------------------------------
Issue & fix info: High Value Fix,Newcomer
Urgency: Normal
Labels: derby_10.9 (was: )
Triage for 10.9. Marking Newcomer and High Value Fix as it should be straight forward and as Brett discovered, it can be quite frustrating when diagnosing a problem to find the diagnostics don't work.
> 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.0.0
> Reporter: Kathey Marsden
> Labels: derby_triage10_9
> Attachments: XATemplate.java, utilXid.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira