db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5553) System property for client tracing -Dderby.client.traceDirectory does not work with XADataSource
Date Fri, 23 Dec 2011 00:59:31 GMT
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:,
            Reporter: Kathey Marsden

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


View raw message