[
https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4709:
-----------------------------------
Attachment: derby-4709-1b-alternative_test.diff
Attached patch 1b, with the following changes:
o changed trace level from TRACE_PROTOCOL_FLOW to TRACE_ALL
o fixed typo
o added logic for closing the underlying physical connection (i.e. for
ConnectionPool and XA data sources)
I also logged DERBY-4717 for the issue with the open trace files, which is
blocking a successful run of the test on Windows.
> Create test that parse client trace file to detect round-trips for Derby-4653
> -----------------------------------------------------------------------------
>
> Key: DERBY-4709
> URL: https://issues.apache.org/jira/browse/DERBY-4709
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Lily Wei
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-4709-1a-alternative_test.diff,
> derby-4709-1b-alternative_test.diff
>
>
> In DERBY-4653, Kristian suggested we have a test that parse the trace file to
> detect round-trip Connection.flowcommit() instead of calling
> getClientTransactionID() method. The existing test for DERBY-4653 is in
> J2EEDataSourceTest.testConnectionFlowCommit(). When this issue get fixed, the
> call for getClientTransactionID can be replace with trace file parsing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
