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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/11/30 11:20:11 UTC

[jira] Commented: (DERBY-4709) Create test that parse client trace file to detect round-trips for Derby-4653

    [ https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965185#action_12965185 ] 

Kristian Waagan commented on DERBY-4709:
----------------------------------------

Lily, can this issue be closed?

> 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.1.1
>            Reporter: Lily Wei
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.7.1.1
>
>         Attachments: derby-4709-1a-alternative_test.diff, derby-4709-1b-alternative_test.diff, derby-4709-1c-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.