db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4709) Create test that parse client trace file to detect round-trips for Derby-4653
Date Fri, 25 Jun 2010 05:41:51 GMT

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

Lily Wei commented on DERBY-4709:
---------------------------------

Thanks Kristian for the explanation and comments. I only want to bring to your attention in
turn of the working theory. While it is true the increase in the number of commit flows caused
by the redundant commits. The verification will be more accurate if we know the increase number
between the base end and unconditional commit. The accurate number does not need to be exact.
However, it will help if it is in a range.  

When I run J2EEDataSourceTest, I am also getting a failure due to the support files directories
are deleted. It will be nice to know we had solved this problem before.

> 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
>            Priority: Minor
>         Attachments: derby-4709-1a-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.


Mime
View raw message